I’m in the same boat here….bugger. Same exact error:
Uncaught TypeError: Cannot read property ‘buttons’ of undefined
I have a plugin that (heavily) leans on ACF and also defines fields by PHP code. This issue is present in ACF Pro (5.7.5 & 5.7.6) but does not appear to be present in the “Free” version (5.7.2) when enabled for early access.
I’m scratching my head here a bit and brainstorming on how to isolate what field might be causing the issue.
Has anyone found a solution or have any clues to share?
Thanks in advance.
Thanks @ajhisbrill, I guess I thought I saw a reference to this setting already being included as a UI element, but I guess I believe I was mistaken.
In any case, the latest versions of ACF & ACF PRO have a new filter included and this solves things for me.
Here’s the new documentation:
Thanks to the ACF team for getting this pushed out!
Hi all, I saw that the changelog of the latest version of ACF PRO (5.3.10) indicates that a new setting field has been added to include Google Maps API keys. I’m super excited to see that this has been addressed…but also a little confused. Perhaps this new setting is right in front of my eyes…but I can’t find it.
Anyone have a clue where this might be located?
Thanks in advance.
Big bump here….does anyone have an update on where this is at for a fix? It does seem like we really need an ACF setting for a site’s Google Map API key. This key would allow the maps to work on /wp-admin/ but then also be accessible to developers for use on front end implementations as well.
Is this approach something that others see as a solution?
Elliot from ACF rules. 🙂 He posted a new version (4.4.7) and it fixes the issue. Three cheers…thanks a million.
Thanks for the update James. What do you think is a reasonable expectation re: a timeline here? A day, couple days, week? Thx in advance.
Agreed….I hope a fix presents itself soon. In a few of my client’s cases I’ve had to roll back WP to pre 4.5 in order to get this working again. One seemingly little detail can really cause big challenges! Is anyone from ACF following this? How can I/we help? Thank you for such an amazing plugin….BTW 🙂
Quick Update & Bump here….
I just installed an entirely new copy of WordPress 4.5 on a test server and have verified that this relationship bug exists using an entirely stock TwentySixteen theme and a fresh copy of ACF (4.4.6).
Thanks in advance.
I updated from 5.2.3 to 5.2.5 and had trouble saving a basic ‘page’ with a few custom fields, nothing with much data. I rolled back to 5.2.3 and all is well again.
Had the same JS error reported in the title (preventing the save).
Just chiming in here that I’m not 100% that this snag has been remedied. Please let me know if I can help any!
Dang…ditto here. I reverted back to 5.1.0 and the errors went away. However, I’ve updated other sites with v.5 and not seen any issues. Anyone have thoughts on what specific combination of fields/repeaters/etc might be causing this? Thanks in advance.
Elliot…thanks so much for your attention to this, but I’m afraid that after updating to 4.3.8, I’m still seeing the issue on my site. In my case, this is a required image field.
If I try to save without an image, I’m prompted to pick one, but then after doing so….I remain unable to save the post.
Thank you for all of your hard work on ACF…it is an amazing plugin.
Yeah…bugger. I have a nested repeater inside a flexible content block that works fine until I enable my conditionals. Once they’re turned on, the admin slows to a crawl with 20-30 second load times….sometimes even killing the page. With the conditionals off, its more like a 3 second load, even with 100 or so total elements (links/file uploads) spread out among 7 “flexible content” blocks and about 30 parent repeater elements. Once loaded, the page saves pretty quickly and the front-end still loads very fast (thanks WPEngine). I’ll likely need to just leave the conditionals off…but it makes the page a lot more cumbersome for my client….fingers crossed here that a solution materializes quickly.
Thanks in advance to anyone that might be working on this.
Elliot….thanks again for your diligent bug-fixing. Everything appears to be working great on my end after the “hotfix” and then the following 4.3.4 update. Cheers!
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!