Problem with Yoast SEO, Text-Editor, Menus and Javascript

Does anyone care about this forum?

Wow, what a support… NOT.

Hello there? Anybody?

The problem exists since months – it is not possible to edit posts with the activated plugin – it is not the case that we as users can solve the problem. It is a problem of the plugin – why does nobody from Yoast answer?

Also the new version 13.1 did NOT solve the problem. I still cannot switch to the text editor and individual menus in the editor are NOT visible when the Yoast SEO plugin is active. In the console you can still find a Javascript Error from Yoast SEO.

Why is this problem not addressed?

Replying to your own topics is considered bumping which is not allowed on the forum. This is because it moves your topic from being considered unanswered. As such, I didn’t see it until I was reviewing older topics.

As to the issue, the JS error shows “URL is not a constructor”. This happens when a setting, plugin or theme is overwriting native JavaScript constructs.

We would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

I have already followed these tips – disabled all plugins, temporarily changed the theme. The problem is Yoast SEO. I’ve been using everything for 7 years, it’s only been occurring since updates of Yoast SEO – the problem is Yoast.

Ok, I tried it with the suggested Health plugin (very helpful). It is not because of a plugin – it is because of my theme in combination with Yoast SEO.

Unfortunately I can’t see now where exactly the problem is ??

This likely means the theme is overwriting a native JavaScript construct that our plugin uses. Please contact the author or support team for your theme developer.

FYI: A few users have reported this occurs for a GoodLayers theme and we determined a line located in the include/include-script.php theme’s file was the source of the problem. The issue was reported to the GoodLayers team for investigation.

Yes, it is a GoodLayer Theme and I solved the problem by excluding the “image-picker” script inside the include-script.php – that caused the problem. I do not use this image-picker (it is for some kind of slider).

I changed the original theme so much that the developer of the theme would not be able to help me, so it would have made no sense to contact them, nearly 80% of the original theme is changed.

Maybe this helps other users of GoodLayers themes as well!