Mark, a heads up. I found this on GitHub as well for ACF. https://github.com/AdvancedCustomFields/acf/issues/218
The guy’s screencast is what I’m experiencing.
Also, when both ACF PRO and Gutenberg 6.4 are active, my ACF Block with a wysiwyg field in it does not seem to initialize the tinymce editor easily when I click into it.
I am having this issue too. It seems to only affect me when I’m using an ACF php block and have the latest Gutenberg editor plugin installed. It does not do this with stock gutenberg (meaning no plugin).
Same issue. Deleted the acf-json folder and the fields in the admin panel and then re-added the folder and sync became available.
Thanks
Hi Just confirming I have the same issue.
Yep, TinyMCE Advanced update worked for me as well. No more conflict that I can see.
It looks like it might be a conflict with TinyMCE Advanced and WordPress 3.9 together?
I updated to 3.9, then updated TinyMCE Advanced. Started getting the error messages.
Then I rolled back the database and files to the previous 3.8 version of WordPress. The tinyMCE Advanced is still upgraded I think, but no more error messages.
Hi, I’d also like to report this issue. I’m getting the same error messages as phantasmix.
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.