Having same problem and i ended in the same as kcalv said about acf_form_head();
And for what i could see the problem start since this change on the wp core:
See how it´s added a new “__ = wp.i18n.__;” into the ColorPicker var.
I guess many other changes in core about i18n and how js uses translations are the problem here, sine i saw many other plugins that are having the same not defined “wp”.
For what i see this is a change that affects many other things, all related on how js uses translations, basicly this:
This removes the usage of
wp_localize_script() for passing translations to the script and instead adds the translatable strings in the script directly through the use of
wp.i18n and its utilities.
Hope this help to find the solution.
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!