[Resolved] Latest Types update causes issue with wysiwyg field in wpml secondary language

[Author]

Posts

[lilyB]

Hi, I'm having the same problem as the person in this thread: https://toolset.com/forums/topic/after-updating-to-new-toolset-types-we-receive-script-error-on-admin/#post-1166292

Since updating Types to the latest version, the wysiwyg field is broken when I edit a page in a WPML secondary language.
In the primary language it works fine but in the secondary language it looks weird & is missing all the buttons (see attached screencaps)...

I'm getting this console error:

Uncaught ReferenceError: wptCallbacks is not defined
    at HTMLDocument.<anonymous> (validation.js?ver=0.1.2:392)
    at i (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-draggable,jquery-u&load[]=i-tabs,suggest,jquery-ui-position,jquery-ui-menu,wp-a11y,jquery-ui-autocomplete,underscore,shortcode,backbone,wp-util,moxiejs,pl&load[]=upload&ver=4.9.8:2)
    at Object.fireWith [as resolveWith] (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-draggable,jquery-u&load[]=i-tabs,suggest,jquery-ui-position,jquery-ui-menu,wp-a11y,jquery-ui-autocomplete,underscore,shortcode,backbone,wp-util,moxiejs,pl&load[]=upload&ver=4.9.8:2)
    at Function.ready (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-draggable,jquery-u&load[]=i-tabs,suggest,jquery-ui-position,jquery-ui-menu,wp-a11y,jquery-ui-autocomplete,underscore,shortcode,backbone,wp-util,moxiejs,pl&load[]=upload&ver=4.9.8:2)
    at HTMLDocument.K (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-draggable,jquery-u&load[]=i-tabs,suggest,jquery-ui-position,jquery-ui-menu,wp-a11y,jquery-ui-autocomplete,underscore,shortcode,backbone,wp-util,moxiejs,pl&load[]=upload&ver=4.9.8:2)

Rolling back the Types plugin to v3.1.2 fixes the problem.

[Nigel]

Hi Lily

I see the issue as reported in the other thread.

I think it would be best if I start with a copy of your own site, if that's okay, to confirm the problem myself after installing the copy locally and performing some basic debug steps.

Let me mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete. And be sure to have a current backup of your site, even though the only change I will be making is to create and download a backup myself.

Can you also confirm a post I can edit to see the problem.

[Nigel]

Sorry Lily, the password does not work.

Can I ask you to try again.

[Nigel]

And which kind of post should I be editing?

[lilyB]

Edit one of the cpt 'profesores' or 'los cursos' in spanish

[Nigel]

I edited the first professor in the list, Roberto Tascini.

I switched back and forth between the English and French versions of the post, and didn't see any problems with the editor, nor any errors in the console. (See screenshots.)

This was on your own site.

If I see something different than you, it suggests you need to clear your browser cache and perform a hard reload.

[lilyB]

Hi,
There's currently no problem on my site only because I rolled back Types to an older version (3.1.2). You can update the plugin if you like & check again. I see a new version just came out though that I haven't tried (3.2.2) yet so maybe it'll fix the problem...?

[Nigel]

OK, yes, sorry, I have a copy of your site so let me update that to the current Types and re-test.

[Nigel]

I get the same result on my local copy of your site after upgrading to Types 3.2.2 and Views 2.7.1, there is no difference editing the French and English versions of the Roberto Tascini post.

However, I did install the backup archive onto a current WordPress site, i.e. using WP 5.0.1.

Checking your debug info I see that you were using 4.9.8.

It seems that updating WordPress will fix the issue, are you able to upgrade?

[lilyB]

That must be it then. I can't upgrade just yet as there's another bug with 5.0+ and the theme I'm using. I guess I'll just keep the old Types version for now until I can upgrade.
Thanks for all your help.

[Nigel]

OK, well sorry for the inconvenience. I know from the developers that not only the 5.0 update but the 5.0.1 and 5.0.2 updates have been a big headache for the whole WordPress community.

I'll mark this as awaiting feedback from you, in case you have anything to share when you get an update for the theme.