This repository has been archived by the owner on Feb 23, 2019. It is now read-only.
Catch Exceptions Thrown When Saving Config #408
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our environment we do not allow the configuration file to be written since we are using a specially constructed file to load some parameters from environment variables. As of 0.9.5.2 this causes fatal errors on any W3TC settings page and on the plugins page in the admin interface.
This is the error:
W3TC\Util_File->file_put_contents_atomic()
throws generic\Exception
if the temporary or final files are not writeable. This is caught inW3TC\Util_Admin->config_save()
for normal configuration save operations (e.g. the Save All Settings button in the admin interface), but not caught when called fromW3TC\Generic_Environment->fix_on_wpadmin_request()
This change adds a try/catch block to catch this exception and push it into
Util_Environment_Exceptions
for handling.Note: The diff is messy since this involves an indentation change and one of the indented lines matches a line at the previous indentation level.