How to Fix Joomla Global Configuration Changes Not Saving
If Joomla Global Configuration appears to accept a change but the old value returns—or Joomla reports that it cannot write the configuration file—the problem is commonly file ownership, permissions, or another hosting-level restriction affecting the root configuration.php.
When Joomla Global Configuration changes do not persist, the usual problem is not the form itself: Joomla must be able to update the root configuration.php. Diagnose the failure by proving that the value reverts, checking the file's ownership and write path, and correcting the server condition without weakening the site's security.
Confirm that saving is actually failing
- Open System → Global Configuration.
- Record the current value of one reversible setting.
- Change only that setting and select Save.
- Record any Joomla error message.
- Reload the page and see whether the old value returns.
If the new value persists but the site still behaves as before, investigate caching or the affected feature instead of file permissions.
Inspect configuration.php ownership and permissions
Using your hosting file manager, SFTP, or SSH, locate configuration.php in the Joomla root. Determine who owns the file and which operating-system identity PHP uses for this site. Joomla needs a server-supported way to write the configuration change. The correct ownership and permission values depend on the host and PHP handler, so copying a numeric permission from another server can create a security problem without fixing the cause.
Do not solve the problem with broad write permissions
A permanent world-writable configuration file exposes sensitive settings and is not an acceptable repair. Correct ownership, group access, the PHP execution model, or the provider's file-permission configuration instead. On managed or shared hosting, ask the provider to confirm the expected ownership and PHP user when that information is not visible to you.
Check less obvious causes when permissions look normal
- A restored or migrated file may belong to an old hosting account.
- A deployment process may overwrite
configuration.phpafter Joomla saves it. - The filesystem or container may be mounted read-only.
- Security software or hosting policy may block PHP file modification.
- Disk quota or filesystem errors may prevent a successful write.
Check server/PHP logs and hosting events around the failed save rather than changing several settings blindly.
Retest after correcting the server condition
- Return to Global Configuration.
- Make one controlled change.
- Select Save.
- Reload the screen and confirm the value persisted.
- Test the site behavior controlled by that setting.
If the value now persists, restore or apply the intended production value and verify it again.
Recover when Administrator cannot be used
If a bad configuration value prevents Administrator from loading, first back up configuration.php. Then use a trusted server-access method to correct only the known bad property or restore a known-good copy. Preserve valid PHP syntax and secure file ownership. If you cannot identify the correct property confidently, restore the backup and diagnose from PHP/server logs instead of guessing.
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.