Apologies, when I sent my last message, your last message from 7:00 wasn't showing for me.
Thankyou for this clarity.
I understand that bugs can be fixed when plugins get updated - but please can you investigate further ASAP, and let me know if an update is the only thing that fixes the issue, or if there's something in the core plugin code itself that's causing this issue and what the resolution is for us?
We are still reviewing this, however, so far the feedback is that this is pointing to the custom theme.
The theme also has some custom code with a hard-coded dependency on the ICL_LANGUAGE_CODE, which can cause Fatal errors when WPML is deactivated.
to help with that we edited the file in question (which is for a language switcher), namely themes/mintcake-flexible/template-parts/language-select.php, and added this to the top:
if ( !defined( 'ICL_LANGUAGE_CODE' ) ){
return;
}
So the WPML-related error disappears.
I would highly recommend contacting the custom theme developers about this issue.
Did you create the theme yourself, somebody in your team or via an external agency?
So I've just switched the theme back to our Mintcake one, gone to the backend of a case studies post, added your code at the top of the php file (just after the opening php tag), refreshed the backend, and I still see the same 2 console errors:
hidden link
post.php?post=8489&action=edit&lang=en:189 Uncaught TypeError: Cannot read properties of undefined (reading 'dispatch')
at post.php?post=8489&action=edit&lang=en:189:13
at post.php?post=8489&action=edit&lang=en:203:6
post.php?post=8489&action=edit&lang=en:932 GET hidden link 404 (Not Found)
I don't see any difference.
It does appear to be theme related, but it's not clear why at all.
ACF managed to create a new post type, create a post, and not see the issue at all, which they're suggesting is transient data interrupting something.
Is ACF's previous statement "The ACFML plugin is throwing a fatal_ wp is not defined _error on a classic editor post type because it is blindly attempting to execute_ wp.data.dispatch('core/notices')_. This crashes the page's JS and breaks third-party interface buttons." not valid in this situation? It seems like a very reasonable explanation as to why the issue is happening, we're using a classic editor which your plugin wasn't expecting and it's breaking the JS on the page.
I have passed this info to our team, however, our plugin does not have any known issues with the Classic Translation Editor.
At the moment it looks like a code within the custom theme is not working well.
It is important to note that custom code support is usually limited.
Are you familiar with your theme's code or would the developer happen to work in your team? It would greatly help to get feedback as well from the theme developer.
My name is Nigel and I am a second tier supporter, and I wanted to communicate with you directly to be clear about the status of this issue, as I understand you are expecting an update.
Although this problem relates to a custom theme and that limits the extent to which we are normally able to help, that is not what is stopping me from resolving your problem, and I do want to help.
The difficulty is that the ACF repeater fields UI does not work with Case Study posts even when all WPML plugins are disabled.
Normally I would investigate a problem where something works, but stops working when WPML is involved.
In this case we have something that doesn't work, and it continues to not work when WPML is involved.
Yes, a JS error appears in the console, but that is not what is preventing the ACF repeater fields working. I will see if I can reproduce the JS error appearing in the console, but it is cosmetic and does not affect the ACF repeater fields. Crucially, if I fix that JS error it will not fix the actual problem you are reporting, which is caused by your theme.
If you check your staging site I have disabled all plugins except for ACF Pro and CPT UI. While your custom theme is active, when editing a Case Study post the ACF repeater fields do not work. Switch theme and then they do work. And if you then activate the WPML plugins you will see that they continue to work.
I suggest your theme developer work on resolving the problem with just ACF Pro and CPT UI active; when it works in that context I expect that it will work when other plugins such as WPML are added to the mix, and if it does not I will look again to identify why.
We'll wait to hear from you to see if further help is needed.
