How to Move the Joomla Log Folder
Choose the new log location carefully
Choose an account-specific directory that PHP can write to and that is protected from normal web access. Joomla's logging documentation uses an absolute filesystem path for the log folder. Do not use a browser URL, and avoid a broadly shared system temporary directory as a substitute for an application log location.
Create the destination before changing Joomla
Create the new directory with the hosting file manager, SFTP, or SSH and apply the ownership, group, ACL, and permissions expected by the hosting platform. The PHP process must be able to create and append log files there. Avoid making the directory world-writable merely to make a permissions error disappear.
Change Path to Log Folder
In Administrator, open System → Global Configuration → Logging and update Path to Log Folder to the verified absolute filesystem path. Save the configuration. Joomla stores this setting in configuration.php, so a failed save can indicate that configuration.php itself is not writable under the server's ownership model.
Use configuration.php only when necessary
If Administrator cannot be used, back up configuration.php and edit only the log_path value with a secure hosting tool. Preserve valid PHP syntax and do not expose the file in a ticket or forum because it contains sensitive site settings. Restore appropriate file protection after the edit.
Verify Joomla can write to the new location
Temporarily enable only the logging needed for a controlled test, reproduce an event, and confirm that Joomla creates or updates a log file in the new directory. Current Joomla programmer documentation notes that the configured log path is the default location used by file loggers.
Handle existing logs deliberately
Moving the configured path does not automatically mean every old log should be deleted. Retain, archive, or securely remove existing logs according to your operational and incident-retention needs. Confirm that no extension is configured with its own custom text_file_path before assuming all Joomla-related logs moved.
Document and monitor the change
Record the new absolute path and why it was changed. After migrations, restores, hosting-account changes, or document-root changes, verify the path again. If logging stops later, check the configured path, disk space, ownership, permissions, and any extension-specific logger configuration before changing Joomla core files.
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.