I upgraded to the latest paid version of toolset types hoping it would resolve the problem. But whenever I enable the toolset types plugin, it breaks the Yoast SEO plugin on the post editing page. It also disables the ability to toggle between code and visual editor. This is in WordPress 5.1.1 running the classic editor.
Thank you for contacting us and I'll be happy to assist.
I performed some tests on my website with Toolset Types and Yoast SEO plugins activated, but couldn't reproduce this issue.
To start troubleshooting, I'll suggest the following steps:
1. Please make sure that the active theme and all plugins are updated to the latest versions.
2. To rule out any third-party code conflict, please test this with all other plugins disabled (except for Toolset Types and Yoast SEO) and a default theme like "Twenty Nineteen".
You also have to install either 'Wordpress Classic Editor' or 'Disable Gutenberg' plugins so that you can test this with the classic editor. Everything works with the new Gutenberg story editor. But if you switch into the classic editor, you should see the problem. Did you try that yet? Many people are not able to use the new Gutenberg editor, which now replaces the classic editor in WP 5.1. So they have to run a plugin to get classic editor back.
I have disabled all plugins and isolated this down to just Yoast SEO, Classic Editor (or Disable Gutenberg) and Toolset Types. The Classic Editor works fine with Yoast until I enable Toolset Types. I've also seen people mentioning this problem during my research with another onthegosystems product - WPML. Possibly it's a related bug?
I'm uploading screenshots of the console messages before and after activating Toolset Types. You can see the errors appearing. Also, I just noticed this is only happening on Chrome but not IE. If you can look into this further with the additional information, I'd appreciate it.
Hey after seeing the issue gone in IE (it was a problem on both previously), I decided to clear browser cached on Chrome. This seems to have fixed the problem. My issue is resolved now. Thank you!
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.