Copy link
If you run into an error while saving Theme Options, you may be seeing a Server Error 500, Server Error 404, Server Error 403, or even a blank page.
Here’s a quick rundown of the most common causes. In my experience, these errors usually point to hosting-related limits or server settings that interrupt the saving process before it can finish.
Please note that Uncode is a rigorously tested and trusted product. If a core feature like Theme Options isn’t saving properly, the cause is usually somewhere in the server configuration. I recommend reaching out to your hosting provider and asking them to check the server logs for the exact error details.
If an error happens while saving, first check whether your System Status shows any warnings about the Memory Limit. The WP Memory Limit controls how much RAM your site can use, and save issues often appear when the server doesn’t meet the needs of a modern WordPress setup.
If you’re still seeing an error, try temporarily deactivating all third-party plugins to see whether one of them is causing the conflict. I’ve seen plugin compatibility issues and performance bottlenecks trigger save failures more than once, so this is always worth checking early.
These errors can also happen when the PHP version is outdated. Make sure your host is using a current stable version recommended by WordPress, such as PHP 7.4 or higher.
Some hosting providers apply strict resource limits. Saving Theme Options can trigger multiple actions at once, and those requests may be blocked by security rules or server restrictions. If that sounds familiar, ask your hosting support team to review the server’s security policies.
Below is an example response from a hosting provider about 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.
Some users have reported that 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 happens, one common fix is to go to: cPanel → ModSecurity → Deactivate.
Once these settings are adjusted, Theme Options should save normally again and your site should run more smoothly. If you still need a hand, please check our documentation or contact our support team.
No comments yet — be the first to share your thoughts.
Save my name, email, and website in this browser for the next time I comment.
Δ
Answers to common Antimanual Builder questions on setup, editing, AI, Pro featur
Learn how Antimanual Builder handles automatic search fields, code stripping, ex
Learn how Antimanual Builder handles security, privacy, external services, code
Configure AI providers, token budgets, migration behavior, and agent memory in A
Learn how to configure Antimanual Builder settings, from AI providers and token
Learn how submenu items behave in Antimanual Builder, including live navigation
Learn how to update or disconnect a live navigation menu in Antimanual Builder P
Learn how to connect a navigation element to a WordPress menu in Antimanual Buil
Learn how to connect WordPress menus to Antimanual Builder pages, manage updates
Learn how Antimanual Builder Pro handles caching for dynamic sections, why pages
Learn how Antimanual Builder pagination works, how to enable numbered pages or l
Learn how Antimanual Builder renders dynamic content on the server, why it matte
Or copy link