ProjectSend
  • About
  • Installation
    • Requirements
    • Manual installation
    • Configuration file
    • One click installers
    • Upgrading
    • Translations
    • Advanced: improving downloads
  • How to use
    • Files
      • File types restrictions
      • Orphan files
      • File size limits
      • Categories
    • Users and clients
      • Creating accounts
      • Self registration
    • Groups
    • Public files and groups
    • Templates
    • E-mail notifications
      • SMTP settings
      • E-mail templates
      • Testing email settings
    • Actions log
    • Cron tasks
    • Custom CSS/JS/HTML
      • Using the assets manager
      • Using custom files
  • Troubleshooting
    • Debug mode
    • Checking php errors
    • Finding and reporting bugs
    • How to get support
    • Collaborate
Powered by GitBook
On this page
  1. Troubleshooting

Debug mode

This is the first step you must take when your instance is returning errors (400, 500) or something just simply does not respond the way you expect

PreviousUsing custom filesNextChecking php errors

Last updated 2 years ago

If you are having issues with your installation, the first step will be to enable debug mode and check for error messages on:

  • Your server's php error log

  • The browser console

  • The browser's network Tab if an ajax request failed

To enable debug mode, edit and find this line

define('DEBUG', false);

Change the value to true like this

define('DEBUG', true);

This will try to enable php's logging and error output features.

If you don't know where the php error log file, you will need to ask your hosting provider for help locating it. In some cases they cannot be enabled on the fly. Just as before, your hosting's support team might be able to enable it for you.

your configuration file