Ok, after a bit of time I see that when using PHP it doesn’t store any fields in the database. So we may have already been getting the benefits of not having to hit the database when using php. Which is good, but it doesn’t address the issue of the Admin still being slow when loading Fields, specifically Flexible Content.
So now the main question is:
If we have already only been using PHP to build our fields do we benefit from using JSON as well?
My initial thought is No, but we would need Elliot to confirm.
I may as well run some bench marks to determine that.
Also I have been playing with exporting fields from PHP to JSON.
I will have a follow up on that soon.
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!