Architect Documentation & Tutorials

Fields not saving

Architect is very powerful but this means Blueprints have many options. This can cause a problem with PHP’s default setting  “max_input_vars”.

In case you encounter this problem with other plugins, I’ve retained this info:

This is a problem that could affect any plugin that saves a lot of information, such as WooCommerce, Gravity forms or Advanced Custom Fields.

PHP has a default limit of max_input_vars of 1000.

If this is exceeded, some fields won’t get saved and will return to their default settings.

It is easily changed by updating your PHP.ini file with this:

max_input_vars = 2000

or your .htaccess with:

php_value max_input_vars 2000

If necessary, please contact your website host and ask them to do it for you.

As WordPress gets used more and more for major applications rather than just blogs and CMSes, this will become a more common problem. However, hopefully, hosts will start changing the default to 2000 or more.

For more information, see these posts:

http://jonathannicol.com/blog/2014/03/02/wordpress-custom-fields-not-saving-phps-max_input_vars-may-be-to-blame/

http://docs.woothemes.com/document/problems-with-large-amounts-of-data-not-saving-variations-rates-etc/

If you are working with WooCommerce, Advanced Custom Fields, or any other plugin that adds many fields to your WordPress, the following plugin is highly recommended for debugging this issue.

https://wordpress.org/plugins/wp-max-submit-protect/p