How to Enable Joomla Error Reporting to Diagnose a Problem
Error reporting can reveal the PHP message hidden behind a blank page or generic server error, but detailed output may expose file paths, code details, and environment information.
Use detailed errors only for diagnosis
Error reporting can reveal the PHP message hidden behind a blank page or generic server error, but detailed output may expose file paths, code details, and environment information. Use it for a short diagnostic window, preferably on staging or during maintenance, and return the site to its normal production setting afterward.
Enable Maximum reporting in Administrator
Sign in to Joomla Administrator and open System → Global Configuration. Select the Server tab, locate Error Reporting, and choose Maximum. Save the configuration, then reproduce the failing page. Record the complete message, file, line number, URL, and time rather than relying on a screenshot of only the last line.
Know what the reporting levels mean
System Default follows the PHP/server configuration, so it may hide messages that the host suppresses in production. None suppresses Joomla-controlled display, while Simple and Maximum expose progressively more diagnostic information. Maximum is appropriate when you need the underlying PHP error during a controlled test.
Use configuration.php when Administrator is unavailable
If the backend cannot load, make a backup of configuration.php and edit the Joomla error_reporting configuration value using an authorized hosting file manager or deployment method. Preserve valid PHP syntax and file ownership. Do not make configuration.php world-writable just to save the change.
Add Debug System only when it provides needed context
Debug System can add stack traces, database/query information, and other diagnostics beyond basic error reporting. Enable it only when the basic PHP message is insufficient, restrict exposure where possible, and never leave debug output visible to normal production visitors.
Check logs when the browser still shows nothing
A fatal error can occur before Joomla is able to render its own error page. If Maximum reporting does not expose the cause, inspect the PHP error log, web-server log, Joomla log directory, and hosting control-panel events for the same timestamp. The server log may contain the only useful message.
Restore safe settings after capturing the error
Once you have the message and reproduction steps, turn Debug System off and return Error Reporting to the site’s normal value. Fix the actual cause, clear only relevant caches, and retest. Error reporting is a diagnostic tool; leaving Maximum enabled is not a repair.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.