Can't save page

If you are experiencing an issue where you get an "ERROR" when saving the page you are working on, please check these troubleshooting steps -

Step 1 Minimum requirements

  • Ensure you are running PHP 7.0 or higher. OptimizePress 3.0 requires at least PHP 7.0 to function properly.
  • Check that you are running the latest version of WordPress. Updating to the latest version of WordPress is highly recommended. WordPress 5.0 is the absolute minimum.
  • Use the latest OptimizePress 3.0 version

Please also check with your hosting company and ensure that your server meets with all the other minimum requirements as provided here -
https://docs.optimizepress.com/article/2020-optimizepress-3-minimum-requirements

Step 2 Check for plugin and theme incompatibilities

Some plugins or theme/s might have a conflict with the OptimizePress 3.0 platform causing this issue. These plugins or theme/s render Styling or JavaScript codes which might break an OptimizePress functionality. Unfortunately we cannot guarantee compatibility with every theme and plugin available for WordPress as there are thousands (over 20,000) of them - we cannot test them all. So we would ask to check your plugins or theme/s if this caused the issue. To do that, please do the following -

If you are not using the SmartTheme, please go to Appearance >> Themes >> then activate any of the default WordPress themes (i.e. Twenty Sixteen, Twenty Seventeen, Twenty Eighteen, Twenty Nineteen), this will deactivate your current theme or the theme you are using in your site. After that, test your issue/s again. If that fixes the issue, your current theme is the cause of the issue/s and is incompatible with OptimizePress 3.0 unfortunately.

To check the plugins, go to Plugins >> disable all plugins except OptimizePress 3.0 plugins. Then check the issue/s. Please note you can reactivate the plugins by going to the Recently Active tab.

Note: We recommend using Chrome or Firefox web browsers when editing your OptimizePress pages, these browsers handle JavaScript best.

Step 3 Increase the max_input_vars of your site

The recommended minimum max_input_vars in the php.ini setting is 3000 - this is usually set to around 1000. If you are having issues in saving the content, please check your max_input_vars is set to the recommended value.

If your max input vars is already set to 3000 and you are still having issues with saving your content, we have heard in few occasions where certain hosts, pages with long content stop rendering or saving content after some point. We found out this is due to a limitation in the PHP setup for the site which is set to only save a certain number of variables on a page. Once the limit is exceeded, content is no longer saved - this is not a setting or limitation within OptimizePress 3.0.

We have found a workaround to solve this issue by increasing the max_input_vars to 10000. You can contact your hosting company and ask them to increase your max input vars.

Or you may do the following (this should only be done once per site and if you are not sure to implement this, it would be better to ask help from your hosting company) -

1. In your php.ini file you need to change the setting for the max_input_vars variable. You need to change it to be 10000:

max_input_vars = 10000

This should ensure that all variables or content is saved to the database rather than only 1000 variables being passed through.

2. If updating through php.ini file doesn't work, then you can try creating a .user.ini file in the same directory as your wp-config.php file and add the same variable:

max_input_vars = 10000

IMPORTANT NOTE: Some hosting companies can't reach 10000 so please ask them their limits beforehand. If they can't reach 10000, ask them to go for max_input_vars = 9999 instead (see more about this at the bottom of this page).

If you are still having issues after doing these suggested troubleshooting steps, please submit a ticket to our support helpdesk so our Support team can check this issue in your site.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.