MyBB

When saving settings in admincp the settings.php chmod is not checked, hence if settings.php chmod gets changed to non-writeable any setting changed in admincp is saved in the database and a success message is also shown but the board continues to use the old values since settings.php could not be updated. What makes this even more confusing for the end user is that the setting value will be shown as changed in the admincp (since its read from the database) even though its not changed in settings.php

The change I propose is to have a check before saving the settings and if settings.php is not writeable throw an error and don't save the setting.

Another addition to this that would be helpful would be to have a banner message in admincp informing the admins that settings.php is not writeable so that it can be addressed.