+1, please
@hube2 sorry, think i was a bit confused when i read how secure you were saying “Yes, changes to ACF are coming to deal with gutenberg, but they are not ready.”
Please leave this opened until a dev finish acf integrations.
@matthias-honert i’m talking to @hube2, just arrived here googling, and i think this topic isn’t closed yet…
FYI and FI of others, Elliot is working on a solution directly with Gutenberg staff on Github… https://github.com/WordPress/gutenberg/issues/12692
+1, 16/01/2019.
Could you please solve this?
The only problem i’m seeing in my code is in case of a field group update, as the “cached” fields are already formatted and if you change return format specs you should update all pages showing those exact fields. I cannot think to hook on save_post for doing this check, as if you have a milion of pages you should first search every page that respects location rules, and then update the fields… maybe it’s better to create a tool which can update all database leaving the user when to use it…
Well, i don’t totally agree with this… if you have multiple option pages and want a single page template to be driven by a particular option page, those options should be loaded by hand only, don’t you think?
I created for you a simple class which should do exactly what i said.
In fact, with 1 query per page now i have all my data ready for a better frontend performance.
You can find the Gist here: https://gist.github.com/teolaz/dc595d5beed29ddad18066d01c237464
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 Cookie Policy. If you continue to use this site, you consent to our use of cookies.