How to Configure Joomla Logging
Joomla can write diagnostic messages from Joomla itself and third-party extensions to its logging system. Global Configuration provides the main logging controls, while extensions can define their own categories and log files. Enable only the logging you need, reproduce the issue, collect the evidence, and then reduce verbose logging when troubleshooting is finished.
Joomla logging can provide the evidence needed to diagnose application and extension problems without exposing detailed errors to visitors. Configure logging deliberately: verify the destination first, enable only the detail needed for the investigation, reproduce the issue, collect the log entries, and return temporary verbose settings to normal afterward.
Open the Joomla Logging settings
- Sign in to Joomla Administrator.
- Open System → Setup Panel → Global Configuration.
- Open the Logging tab.
- Record the current settings before changing them.
The available controls include the log-folder path and options for broader, deprecation, priority, and category-based logging.
Verify the log folder before enabling more logging
The configured log path must be a valid absolute filesystem path writable by the PHP process running Joomla. Prefer a protected location that is not directly downloadable from the public web. If the path is missing or unwritable, correct the path, ownership, permissions, or hosting restriction before relying on the logs.
Choose the logging level for the investigation
Log Almost Everything is useful for a short troubleshooting window when broad application logging is needed. Log Deprecated API is more appropriate for compatibility testing and can be noisy on a production site. Custom priorities and categories are useful when Joomla or an extension documents a specific category to capture. Avoid enabling every diagnostic option indefinitely.
Reproduce the problem and verify the log output
- Save the logging configuration.
- Note the current time.
- Perform the exact action that fails.
- Open the configured log directory and identify files updated at that time.
- Match timestamps, categories, priorities, and messages to the test.
If no relevant entry appears, confirm that the component actually logs the event and that any required category is configured correctly.
Finish troubleshooting cleanly
Save the useful evidence, redact secrets before sharing it, and turn off temporary broad or deprecation logging that is no longer needed. Monitor log growth and disk space. If a third-party extension writes to its own file or directory, follow that extension's logging configuration rather than assuming every message must appear in Joomla's global log folder.
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.