Update to WP 3.8 did not solve the problem. But I’ve increased the PHP default value from php_value max_input_vars 1000 to 3000. This did solve the problem. The field group I use has about 65 added entries. This gives at least 15 input vars per entry. This may help to estimate the necessary value of max_input_vars for others.
Hi @elliot,
When layouts get lost after saving they are not available for selection on a post edit page any more. But as long as I don’t save the post the lost layouts will be displayed correctly on the front end.
When I delete a layout (which contains 20 subfields) from the flexible content field, saving of the whole field group succeeds. Also adding a new layout afterwards, saves succesfully. But adding many subfields to that new layout resulted in a failure again. Deleting additionally another layout with nearly 20 subfields allowed me to save the new layout successfully.
Creating and displaying a new field group containing a flexible content field is no problem.
Also execution time is no problem. Other processes which need about one minute have finished successfully.
Is it possible, that WP limits the number of max_input_vars?
I’ve exactly the same problem with a flexible content field now (acf v4.3.2 / Flexible Content Field v1.1.0).
I did succesfully change the field group with older versions of ACF. The last change is about half a year ago. PHP value max_input_vars has always been 1000. Also there is plenty of memory available (256MB and page requests need about 60MB).
The error already occurs if I simply change the value of ‘Maximum Layouts’. When saving this value is not stored, also the value of ‘Button Label’ is reset to the default and the last three layouts of the flexible content field disappear. But a change of the label field at the top is successfully saved. When exporting the field group in a xml file the missing layouts are not contained any more.
When importing an earlier backup the missing layouts are back again. I’ve tested this on two servers.
Do the newer versions of acf use much more input vars than before? Or may it be a bug in the plugin which cuts the input stream?
