Conflict with Yoast SEO ?

This support ticket is created 4 years, 10 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.

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: Views plugin

This topic contains 7 replies, has 2 voices.

Last updated by Shane 4 years, 10 months ago.

Assisted by: Shane.

Author

Posts

January 10, 2020 at 4:09 pm #1451273

Gian Luca

Yoast SEO is not working on my CTP anymore. By default, it will not even show up when editing CPT. If the block editor is active, clicking the yoast icon in the editor will trigger the following error:

ReferenceError: YoastSEO is not defined
at a (hidden link)
at e.exports (hidden link)
at t.value (hidden link)
at re (hidden link)
at Vg (hidden link)
at ph (hidden link)
at lh (hidden link)
at O (hidden link)
at ze (hidden link)
at hidden link

January 10, 2020 at 8:20 pm #1451605

Shane

Supporter

Languages: English (English )

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

Hi Gian,

Thank you for getting in touch.

Actually i'm not aware of any conflict between toolset and yoast, so it could be another plugin that is causing this.

What I recommend that you do is to temporarily disable all the non-toolset plugins with the exception of Yoast and see if the issue still remains.

Thanks,
Shane

January 10, 2020 at 8:25 pm #1451623

Gian Luca

Hello Shane. I actually tried that, but the error is still there even with all plugins disabled, except Yoast and Types.

January 10, 2020 at 9:15 pm #1451713

Shane

Supporter

Languages: English (English )

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

Hi Gian,

This works perfectly fine on my end.

Would you mind allowing me to have admin access to the site so that I can grab a copy to test here locally?

The private fields will be enabled for your next response.

Thanks,
Shane

January 13, 2020 at 9:00 pm #1456791

Shane

Supporter

Languages: English (English )

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

Hi Gian,

Thank you for the credentials, I was able to successfully log into the site.

Just for clarity Any post type that has the block editor enabled on it produces this error correct? Even the wordpress default post type correct?

Please let me know.
Thanks,
Shane

January 14, 2020 at 8:43 am #1457443

Gian Luca

Nope. Just the post types created with wp types face the issue.

January 14, 2020 at 9:30 am #1457607

Gian Luca

I had to downgrade Yoast to ver. 12.7.1 in order to have it work. I confirm there is a conflict somehow. I'll post the issue to Yoast support forum as well.

January 14, 2020 at 2:31 pm #1458005

Shane

Supporter

Languages: English (English )

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

Hi Gian,

Yes you can have them look at the issue since it is breaking.

However I'm trying to actually see the issue but the Yoast option doesn't appear on any of the custom post types.

I'm also not seeing any JS error in the console on my end. I'm only seeing the yoast option on the default Post.

Thanks,
Shane