Hi James, you know? it´s happening again, i have only 4 pages, using just in one of them, 2 flexible layouts with really not too many fields… 11 seconds to save.
I thinks it´s something with js that takes a lot of time checking one by one if some has change… is that correct?
If that, there must be a way to avoid it and only save directly the ones changed. The changed status could be something applied to the field once is changed, like adding a class “changed”, then, the save process will only take those “changed” fields to save, and no need to check one by one. Or i´m missing something important behind the script that can´t do that way things?
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!