Finally! What a ride. Glad for being part of this thread since 2017.
Thanks a lot for adding that feature!
That’s a great feature request!
Especially after clicking the shortcut to edit a field group (gear icon in page/post edit screen) you won’t have any clue that you are currently editing an unsynced field group.
+1 can’t understand why this is marked as solved
+1 to make some noise.
It is really time consuming that any member of my team and I constantly have to re-enter the keys on all our computers for local development and on every dev, stage and prod environment after every single sync of the database.
@matt-anchour this is exactly what we are experiencing over here.
the JSON file is being interpreted correctly while using the “edit post” screen but gets messed up while loading the “edit field group” screen. Saving the field group then results in a messed up JSON file.
Hopefully a bugfix is being released soon.
I can confirm two things:
The JSON file is in the correct order and the acf fields while editing a page are also in the correct order but when I want to edit a field group all fields within the field group are being randomly reordered (always the same fields are affected) and this state will be written into the json file on save.
This is a very huge problem because editing ACF fields is just unusable right now. Having to reorder multiple fields after changing one property is really slowing down our workflow.
This bug is really grinding my gears. Any idea when the bugfix will be released? It’s a huge pain in the a** that every developer has to constantly check the diff before committing the JSON file after saving a field group.
@ohnojono that’s indeed a great idea! We are facing exactly the same problems while handling a project with 40 different layouts.
Any news on that one?
I’m quite disappointed that this is not solved, yet. I would also be happy to pay an annual fee for that and all the other awesome features of ACF.
@elliot Any progress on this issue? It’s been marked as solved but it seems like a lot of people would love to see a solution to persistently store the ACF license key in a file.
It seems like the options page itself does not contain a language switch in the “publish” section.
However, you should be able to switch the active language by clicking the flag in the dark toolbar at the very top of the admin area.
Works perfectly for me on various websites.
+1 from me.
I also have to re-enter the license key several times a day on different sites because of this problem.
Would be a huge time saver.
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.