Copy link
If you encounter an error when saving Theme Options, you may be experiencing a Server Error 500, Server Error 404, Server Error 403, or a blank page.
Below is a compilation of common causes identified over time.
Typically, these issues relate to hosting resources that interrupt the option-saving process.
Please note that Uncode is a rigorously tested and trusted product. If a core function like the Theme Options fails to operate specifically within your installation, the issue is likely rooted in server-side settings.
We recommend contacting your hosting support team to investigate the server error. Request that they verify the specific error details found in the Error Log file.
If an error occurs while saving Theme Options, please verify that there are no warnings regarding Memory Limit within your System Status. The WP Memory Limit defines the maximum amount of RAM your site can utilize simultaneously.
Memory limit issues typically arise when the server environment does not meet the requirements for a modern WordPress configuration.
If you encounter an error, attempt to deactivate all third-party plugins to determine if this resolves the issue. Conflicts or performance bottlenecks caused by external plugins are a common cause.
Errors may also stem from an outdated PHP version. Ensure your host provides the latest stable version recommended by WordPress, such as PHP 7.4 or higher.
Certain hosting providers impose strict resource limits. Saving Theme Options triggers multiple simultaneous actions that may be blocked by these restrictions. Please request that your host review these specific settings.
Below is an example response from a cooperative hosting provider regarding this issue:
Yes, it seems that you triggered one of our security measures called Mod Security. It appears that the delete function is causing multiple backend calls simultaneously, which is causing the system to malfunction. However, we have disabled this rule since it only applies to the admin area, so there should be no increase in the risk of any account exploits.
Users have reported instances where the saving process was blocked by a server-side pattern match:
Request: POST /wp-admin/options.php Action Description: Access denied with code 403 (phase 2). Justification: Pattern match "(?i)([s"'`;/0-9=x0Bx09x0Cx3Bx2Cx28x3B]+onw+[sx0Bx09x0Cx3Bx2Cx28x3B]*?=)" at ARGS:_uncode_post_custom_fields_settings_array.
A common solution involves navigating to: cPanel → ModSecurity → Deactivate
Addressing these potential issues helps ensure the Theme Options save correctly and maintains optimal website performance. For further assistance, please refer to our support documentation or contact our support team.
Save my name, email, and website in this browser for the next time I comment.
Δ
The Backup functionality in Changeloger ensures that your configuration settings
The Product Notification Settings in Changeloger Pro allow you to maintain activ
n The Version Tracking Settings feature in Changeloger Pro enables your site to
The User Authentication settings in Changeloger provide granular control over ho
The Roadmap Settings in Changeloger Pro provide comprehensive controls for manag
n The Feedback Settings section in Changeloger provides comprehensive control ov
n The Releases Settings provide granular control over how your product updates a
The General Settings in Changeloger allow you to configure the core behavior and
The Global Plugin Settings in Changeloger serve as the primary control center fo
All plugin configurations for the Changeloger suite are centralized within the W
n Changeloger offers versatile embedding capabilities, allowing you to seamlessl
The Changeloger plugin provides robust Embed Settings, allowing you to display y
Or copy link