How to Change the Joomla Log Folder
Joomla's log folder is the filesystem location used by Joomla's file logging unless a logger or extension explicitly chooses another path. Change it carefully: Joomla's official Global Configuration help warns that an invalid or unwritable log path can prevent the site from loading.
Joomla's log-folder setting controls the default filesystem location used for Joomla file logs. Change it carefully because an invalid or unwritable path can interfere with logging and may cause application problems. Prepare the destination first, save the absolute path, and verify that Joomla can write to it before considering the move complete.
Prepare a safe destination
Create or choose a directory intended for Joomla logs. It must exist and be writable by the PHP/web-server identity serving the site. Prefer a location protected from direct public downloads. Use provider-approved ownership and permissions; do not make the directory world-writable as a shortcut.
Change Path to Log Folder in Global Configuration
- Sign in to Joomla Administrator.
- Open System → Setup Panel → Global Configuration.
- Open the Logging tab.
- Enter the destination's absolute filesystem path in Path to Log Folder.
- Select Save or Save & Close.
Enter a server filesystem path, not an HTTP or HTTPS URL.
Verify that Joomla is writing to the new location
Reopen Global Configuration and confirm the path was retained. Trigger a known loggable event or temporarily enable the logging needed for a controlled test. Then confirm that a log file is created or updated in the new directory with the expected timestamp. If not, inspect ownership, permissions, ACLs, storage limits, and PHP path restrictions.
Recover from an invalid path
If Administrator becomes unavailable immediately after the change, restore the previously working log path in Joomla's root configuration.php using a safe filesystem editor. Back up the file first, preserve valid PHP syntax, and change only the log-path value. Once the site loads again, verify the path from Global Configuration and test logging.
Account for extensions and future migrations
Third-party code can configure a different logging path, so one extension may continue writing elsewhere even when Joomla's global path changes. Also recheck the absolute path after moving the site to another server because account and filesystem layouts often change. Keep log directories protected, monitor disk usage, and include the working path in migration documentation.
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.