Cannot save Global Configuration changes
From Joomla! Documentation
This article is a small, well-defined item that could be completed by someone with a reasonable knowledge of the subject matter and a modest time commitment. If you would like to try writing this article you're welcome to do so.
The subject may be self-evident, but if not then further details should be available on the discussion page. Please add {{inuse}} at the top of this page while editing. For other small, well-defined tasks, please look in the Cookie jar. ---Thank you. This article was last edited by Coala (talk| contribs) 15 years ago. (Purge) |
This article is a stub and needs to be expanded. If you can provide information or finish this article you're welcome to do so. Please remove this message afterwards or replace with {{inuse}} while making major edits. - Thank you. |
This problem is usually caused by incorrect ownership or permissions on the configuration.php file which is where the Global Configuration settings are stored. On some Joomla! installations the configuration.php file is set to read-only as an additional security measure.
Solution:
In order to bypass this problem and save your configuration changes you will have to have access (ftp or ssh) to the webserver hosting your joomla site and change the permissions of the configuration.php file. Usually most hosting providers permissions scheme, comes in the form: owner(ftp_username), group (webserver username), others (word readable). If that's the case, then use your ftp client to give write access to the group of the file. If you use an cli terminal, you can go to the root path of the joomla site and execute the following command:
#chmod 660 configuration.php
!!Note!! As mentioned above this a potential security risk, so if you complete the changes, you should change to permissions 640 which is rw-r----.