I don’t think you’ll have a lot of problems with timing out with the type of data you’re using. You already have a upper limit on the number of rows that can be added. PHP has a setting for max_input_vars which is 1000, in your scenario you have 186, well below this threshold, so again, you shouldn’t have a problem here.
Custom coding an application could be more stable or not, really depends on how it’s coded and how it works.
Are you running into an issue with max_input_vars? This can be a problem on large groups of fields. Try installing this plugin and making edits. The plugin has not been updated in a while but it still works https://wordpress.org/plugins/wp-max-submit-protect/
When having problems with large numbers of fields you are usually running into an issue with the PHP max_input_vars setting. More information here https://www.advancedcustomfields.com/resources/limit-number-fields/
The developer took my advice. All versions since 5.0 no longer have this problem.
You can change your max_input_vars setting back to the default value of 1000, and ACF will work fine with large field sets.
Hope this helps others, but for every WP site I set max_input_vars to 5000. Since then I have run dozens of sites and some with massive amounts of repeaters and other fields. So far I have not run into this issue again.
You can do this with Apache or Nginx (Whatever web server you are using) or PHP.ini.
The most common reason that values to not update is the max_input_vars PHP setting https://www.advancedcustomfields.com/resources/limit-number-fields/
No idea if this would help, but have you tried changing the max_input_vars in php.ini?
https://www.advancedcustomfields.com/resources/limit-number-fields/
This is happening for me. Checked max_input_vars and it should be displaying…
Thanks @wp_kc – it appears to be fixed by increasing the max_input_vars to 2000
As far as I know the only solution currently is to increase max_input_vars and leave it.
The developer may focus on this in the future, but I don’t have this information. The best way for you to get his attention is here https://www.advancedcustomfields.com/contact/
PROBLEM SOLVED! It was MY code. I missed the “=”. So I hade “max_input_vars 5000” when it should have been “max_input_vars = 5000”
Plugin is now showing Field limit: 5000 and I a can save the nested repeater.
So yesterday, I added the max_input_vars to my .htaccess file. No change. I then contacted my host about adding it to my php.ini file. Which is only accessible via SSH. Something I don’t work in. After much hand holding from my host’s tech support, I was able, through Mac Terminal to get into the php.ini file and change the commented out max_input_vars to uncommented and changed the 1000 to 5000. After all that, the plugin still says the max vars is 1000 and my ACF repeater will not save. Not sure what else to do. Not sure if rebuilding my ACF form in a different way would make a difference. For instance, I could make the parent repeater, not a repeater and instead make each of those individual repeaters. So that their is no nesting. But they are still all on the same page. It might make fewer vars but I think I would still hit 1000 pretty quickly.
The only possibility that I know of is max_input_vars, but it could be suhosin.post.max_vars or suhosin.request.max_vars also needs to be set. Try this plugin https://wordpress.org/plugins/wp-max-submit-protect/
You’re problem is probably related to your php_max_input_vars setting.
Try installing this plugin, it’s old but it will tell you if this is the problem https://wordpress.org/plugins/wp-max-submit-protect/
There is a plugin that will alert you to problems with max_input_vars https://wordpress.org/plugins/wp-max-submit-protect/
I use this plugin on all sites that I’m developing.
I found resolve for this problem 🙂 I change value for max_input_vars in php.ini for 10000 and all is OK.
I think that should be notice before save about this problem because peopl can lost their changes
you can test something similar:
(php.ini)
max_input_vars = 20000
suhosin.get.max_vars = 20000
suhosin.post.max_vars = 20000
suhosin.request.max_vars = 20000
I am having a similar issue. I imported ACF fields into a new site, with content from three old sites. The fields are completely uneditable though, and I can’t create new fields in any way either.
I upped max_input_vars, and checked all settings, but nothing seems to help. I also removed the plugin and re-added. Any ideas would be helpful.
If there’s a problem with max_input_vars, this will tell you about it so that you can fix it. The only solution for max_input_vars issues it to alter the php setting. Doing this will be different depending on your hosting. For all I know, some hosing providers do not allow it to be changed.
If the issue is not max_input_vars and you don’t get a warning from this plugin then you can stop looking into solutions for this problem and look for something else, although given what you’ve said I don’t really know what else it could be.
Hi John,
As I investigated the plugin that you suggested, I understood that this is not a solution for “max_input_vars” problem on ACF. This is just a pop-up warning for users. Actually, we don’t solve the problem with this plugin, just inform the user about the problem.
Is there any other solution for ACF’s “max_input_vars” problem?
to know it it’s related to max_input_vars install this plugin https://wordpress.org/plugins/wp-max-submit-protect/. If there are too many inputs this plugin will pop up a warning telling you what you have it set to and how many you are attempting to submit.
Hi John,
Actually, there is not any timeout problem on our ACF pages. The problem is that sometimes if we add too much content on a page and if we update or save that page, total or half of the page content gets lost.
To overcome this problem, we have tried to apply your suggestions in your first comment. And we have changed the values of some input parameters. But at the end of our tests, we couldn’t find any rational and visible relation between the input length parameters and the page content loss.
The “values/test results” relation has occurred in like the list below.
-If the max_input_vars = 999999999999999999999999999 => no content loss
-If the max_input_vars = 999999999999999999999999999 => content loss
-If the max_input_vars = 1000 => content loss
-If the max_input_vars = 9223372036854775807 => no content loss
-If the max_input_vars = 999999999999999999999999999 => no content loss
-If the max_input_vars = 1000 => no content loss
-If the max_input_vars = 999999999999999999999999999 => no content loss
-If the max_input_vars = 999999999999999999999999999 => no content loss
-If the;
max_input_vars = 1000
suhosin.get.max_vars = 1000
suhosin.post.max_vars = 1000
suhosin.request.max_vars = 1000 => content loss
-If the;
max_input_vars = 999999999999999999999999999
suhosin.get.max_vars = 999999999999999999999999999
suhosin.post.max_vars = 999999999999999999999999999
suhosin.request.max_vars = 999999999999999999999999999 => no content loss
As you view, there is not a visible relation between the values of the parameters and their test results.
Now we are stuck in the solving the content loss problem on ACF pages. We want to learn that; in which other conditions can page content loss occur?
What your describing is a symptom of PHP max_input_vars issues. Try installing this plugin and see if you get a warning when you try to submit your form https://wordpress.org/plugins/wp-max-submit-protect/
