Some WP users may find Architect does not save all values. This is not actually a bug in Architect, rather the way default PHP installations are configured with a limit on maximum variables that can be saved.


There are thousands of posts on this issue just in regards to WordPress around the internet!


Here's a couple worth reading:


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


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


Solutions:


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


max_input_vars = 2000


or your .htaccess with:


php_value_max_input_vars 2000


If that is too technical, contact your host.


It's probably too technical to explain the whys and wherefores here but if you are displaying custom fields with Architect, you will almost certainly need to adjust that setting.


If you are using your own CSS or Headway's, and not using Architect's built in styling, you can turn styling off in Architect > Options > Use Architect styling which will greatly reduce the number of values in your Architect Bluepritns and will probably avert this unless you have a lot of custom fields in the Blueprint.


With WordPress used for much more than blogs and CMSes nowadays, this is an issue that is going to affect a lot of WordPress websites whether or not they are using Architect.