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.
Open Joomla logging settings
- Sign in to Joomla Administrator.
- Open System → Setup Panel → Global Configuration.
- Open the Logging tab.
Current Joomla help documents Path to Log Folder, Log Almost Everything, Log Deprecated API, and custom logging controls on this tab.
Verify the log folder first
Path to Log Folder must be an absolute filesystem path that PHP can write to. Joomla's documentation warns that a missing or unwritable logging path can prevent Joomla from loading, and advises against a system-wide location such as /tmp. Keep the configured path protected from unintended public access.
Use Log Almost Everything for focused troubleshooting
Set Log Almost Everything to Yes when you need broad diagnostic logging. Joomla programmer documentation states that this records categories other than deprecation messages in everything.php. Reproduce the problem, inspect the resulting log, and turn broad logging back down after collecting what you need so the log does not grow unnecessarily.
Handle deprecated API logging separately
Log Deprecated API controls deprecation logging separately. This is useful when testing extensions against newer Joomla/PHP environments, but it can be noisy. Enable it intentionally during compatibility work rather than assuming it is required for ordinary production operation.
Use priorities and categories for custom logging
The custom logging controls let you select Log Priorities and specify Log Categories. Joomla's logging API uses standard severity-style priorities and category strings. If an extension documents a specific category, use that exact category. An empty category configuration means custom logging is disabled according to Joomla's Global Configuration help.
Verify that logging works
- Save Global Configuration.
- Perform the action you want to diagnose.
- Inspect the configured log directory for a newly written or updated log file.
- Confirm the timestamps and messages correspond to your test.
- Disable temporary verbose/deprecation logging when finished.
If no file is written, confirm the configured path exists, PHP can write to it, and the event/category you expect is actually being logged by Joomla or the extension.
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.