Skip Navigation

[Resolved] Javascript error on wp-admin that prevents changing in the visual editor to html

This support ticket is created 5 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Our next available supporter will start replying to tickets in about 2.40 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by enma 5 years, 9 months ago.

Assisted by: Shane.

Author
Posts
#1195980
types-error.jpg

I cannot change in wp-admin between visual and html editor.
The error only occurs with custom types, not with pages and posts.

The following javascript error appears in the console:
Uncaught TypeError: $headers.imagesLoaded is not a function in
/wp-content/plugins/types/vendor/toolset/toolset-common/toolset-forms/js/file-wp35.js?ver=0.1.2

The site is updated to the latest version of wordpress and types.
I have tried to disable all plugins but the problem persists.

#1196111

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Enma,

Thank you for contacting our support forum.

Since you've already tried disabled the non-toolset plugins there is no need to do this again. What I would like for you to do for me is to provide me with a copy of your site if possible.

This way I can investigate the issue further and also to ensure that it is also not a server issue.

To provide a copy of your site please follow the instructions in the link below.
https://toolset.com/faq/provide-supporters-copy-site/

Thanks,
Shane

#1196264

My issue is resolved now. Thank you!