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 summary of common causes for this issue. Typically, these errors are related to hosting resources that interrupt the data-saving process.
Please note that Uncode is a rigorously tested and trusted product. If a core feature such as Theme Options fails to operate, the issue is likely rooted in server-side configurations. We recommend contacting your hosting provider to investigate the server logs for specific error details.
If an error occurs while saving, please verify that there are no warnings regarding Memory Limit in your System Status. The WP Memory Limit defines the maximum amount of RAM available for your site. Issues often arise when the server environment does not meet the requirements for a modern WordPress configuration.
If you encounter an error, temporarily deactivate all third-party plugins to determine if this resolves the conflict. Performance bottlenecks or compatibility issues caused by external plugins are a frequent cause of save failures.
Errors may also stem from an outdated PHP version. Ensure your host supports the latest stable version recommended by WordPress, such as PHP 7.4 or higher.
Some hosting providers enforce strict resource limits. Saving Theme Options triggers multiple concurrent actions that may be blocked by these security restrictions. Please request that your hosting support team review your server’s security policies.
Below is an example response from a hosting provider regarding this issue:
It appears that our security measure, ModSecurity, was triggered. The backend process was initiating multiple simultaneous calls, causing the system to block the request. We have disabled this rule for your admin area to prevent further interference.
Users have reported instances where the saving process was blocked by server-side security rules:
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.
If this occurs, a common solution is to navigate to: cPanel → ModSecurity → Deactivate.
Addressing these configurations will help ensure that Theme Options save correctly and your website maintains optimal performance. For further assistance, please consult our 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