Home › Forums › General Issues › Slow update with field heavy page › Reply To: Slow update with field heavy page
I don’t know this to be a fact, but I’m assuming that there is something built into ACF that does a simple “has something changes or not” test. If nothing has been changed in an ACF field then the data is just sent.
If something has been changed then the JavaScript needs to look at every field, is it a required field? If it is, does the field have conditional logic that may have it hidden and then not require.
You can also create custom filters for what is allowed input in every field and I’m pretty sure this means that checking the data requires an AJAX call so that custom filters can be run and errors returned, so the larger the number of fields the more data that needs to be sent and returned during the request.
The answer to your question is that, all of the data is updated, but that’s not what’s slowing it down. Unfortunately I think this is just a side effect of the way that the work needs to get done.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.