ACF has advised that this might be due to “hitting a limit on the number of variables that can be used on a single page load on your server”.
We followed their instructions to edit the php.ini file on the server and add max_input_vars=3000 and it seems to have fixed the issue.
Hi @johnstew
It is possible that you are hitting the max_vars limit on your server and you can fix this by making the following changes to your php.ini file:
max_input_vars = 3000
suhosin.get.max_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
Let me know if this helps.
Hi @saadsohailk
This is possibly due to PHP limiting the number of variables.
Try to increase this by adding
max_input_vars = 3000
In you php configuration.
Let me know if it helps.
Hi @thestart,
Thanks for the post.
It is possible that your server is terminating the save process before ACF can finish the field’s save process.
Please increase your max_vars setting by making the following changes to your php.ini file:
max_input_vars = 3000
suhosin.get.max_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
Hi @gwenzez
Thanks for the question.
There is no limit to the number of custom fields that can be added to a field group or in your case the repeater. Your server might be terminating the save process before ACF completes its job, you will need to increase the max_vars PHP setting. You can make the following changes to your php.ini file:
max_input_vars = 3000
suhosin.get.max_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
The WSOD might also be as a result of a plugin conflict, please deactivate all other installed plugins and switch to one of the stock WP themes to check if the issue will still pop up.
To update the plugin you will need to log in as an admin.
Thanks for the responses. I’m actually on a dedicated server, so increasing the memory really does increase the memory. And yes, I’m sure that my max_input_vars and memory limit are correct by verifying in the php info.
I added these:
max_input_vars = 3000
suhosin.get.max_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
Per the FAQ, although I bumped those all up to like 16000 with still no results. And memory is at 800MB currently.
I was in the process of adding new fields when this started happening. I had to add 7 and I made it to 5 before it stopped working for the final 2. So I’m sure that no other plugins were updated or installed and I’m certain nothing else on the site was being changed either during the additions. It just decided to stop at 60 and making these changes hasn’t worked. I’ve also checked the database manually to be sure that it wasn’t some display issue, but the new entries I created (that ACF said were created successfully) are not in the database either. Thanks again.
Hi @bruno-martins
I am not sure what you mean by “It does not work” is the Repeater field not saving values? If this is the case, it may be related to the field_name length.
ACF uses the field’s name to save a value into the database. When saving sub fields, the ‘save name’ is generated by the ancestors names + the row index and can become quite long. It is possible that the length of this ‘save name’ can become too long for the wp_options table, and WP will not be able to save the value at all.
You can solve this by reducing the field name length.
If the issue is to do with the field not saving, you can make the following changes to the php.ini file:
max_input_vars = 3000
suhosin.get.max_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
Thanks Hube2. I have been developing locally in MAMP Pro. Here is what I did after some research into the solution you recommended.
I increased this ‘max_input_vars = 3000’.
In MAMP that is under File > Edit Template > PHP
ok … looks like this is caused by the new default max_input_vars=1000 in php.ini. Changing that limit to 3000 solved the issue for me.
Maybe it is possible to add a check into ACF to issue some kind of information or error if this happens?
There’s some similiar types of issues on the forum here:
http://support.advancedcustomfields.com/forums/search/?bbp_search=max_input_vars+%3D+3000
What solved my issue was dropping the following into the top of my WP site’s .htaccess file:
php_value max_input_vars 7000
After much research and much reading… I found the answer via another post on this website. I had to increase my php settings to allow more variables to be inputed.
max_input_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
The post with the answer:
http://support.advancedcustomfields.com/forums/search/?bbp_search=max_input_vars+%3D+3000
Eliot, I know this issue is not related to your plugin, but just a php setting. However since it seems like a few people have already experienced the same issue, maybe you could have common solutions as this one placed somewhere easy to find in your support forum.
Silly me, of course the answer was not number of fields, but number of post vars…
72 fields just happened to push the post vars count over PHP 5’s default limit of 1000. This issue also crops up with really large menus in WP.
The fix:
Add a php.ini file to /wp-admin/ and put these settings in there (assuming your host allows php.ini overrides):
max_input_vars = 3000
suhosin.post.max_vars = 3000
suhosin.request.max_vars = 3000
From: http://anothersysadmin.wordpress.com/2012/02/16/php-5-3-max_input_vars-and-big-forms/
acf-zora-cre....txt
