• Resolved scruffy1

    (@scruffy1)


    Hello,

    Just updated to latest, disabaled jquery helper plugin and the issue (missing yoast controls etc) with Yoast is still the issue with WP 5.5, unfortunately.

    Thanks,

    Tracey

Viewing 15 replies - 1 through 15 (of 16 total)
  • Same for me.

    Hi @scruffy1,

    Thank you for creating this topic. The patch release was related to another bug in WordPress also causing Javascript issues, but not directly related to the jQuery Migrate drop in WordPress 5.5.

    If you do have issues with jQuery Migrate, this is not coming from our plugin as we don’t depend on this. This would come from your theme or any other plugin on the site that is causing issues and therefore Yoast possibly fail to load completely.

    We’d encourage you to find the culprit while doing a conflict check with the steps found here: https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/.

    Hope that explains.

    Thread Starter scruffy1

    (@scruffy1)

    Hello,

    The only change which resulted in Yoast not working was upgrading WP to 5.5 before this it worked.

    Yoast, quite simply does not work with WP 5.5. Whatever it may be. Be it a WP issue or a Yoast issue. However with the helper plugin Yoast works.

    Thanks Tracey

    • This reply was modified 4 years, 3 months ago by scruffy1.

    Hi @scruffy1,

    Thanks for confirming that it works with the jQuery Enabler plugin. Please do know that this is considered a temporary workaround because the real cause needs to be addressed. Meaning that a theme or plugin on your side depends on the old code. If you do the conflict check, you’d be able to narrow this down so you can contact the theme or plugin developers so they can fix that.

    Thread Starter scruffy1

    (@scruffy1)

    Jeroen,

    I have contacted Madras Themes and they assure me their theme is compatible with WP 5.5.

    Because these are live sites that have to be SCA safe etc and I am contracted to maintain that level of security, I am not about to start testing different plugins.

    Neither site uses all the same plugins apart from a couple such as Yoast and Woo. I cannot see how either the theme or a plugin can be the issue for your plugin. Granted I am not a coder but I am more confused with this than ever.

    I still maintain it is either a WP 5.5 or a Yoast issue.

    I have been in touch with the WP team and see if they can offer any light on this.

    Thanks

    Hi @scruffy1,

    Thank you for your reply.

    We understand that you are confused about why Yoast might fail to load. Our plugin depends heavily on react and Javascript to be functional. WordPress 5.5 was a major update and dropped the enqueuing of an old script named jQuery Migrate. A lot of older plugins and themes were relying on that script to be present, and if so, it can cause Javascript errors to occur. When this is the case, any Javascript error that is occurring might be causing Yoast SEO to load (completely).

    We understand that you might not be able to test these things on your live site, in that case, we recommend to troubleshoot this on a temporary staging site to investigate this. It’s good that you know that the theme should be okay, but you can also test this during the troubleshooting.

    Hope this explains the issue at hand a little better.

    Watch out. Themes may be compatible with WP 5.5.
    But you should review the possible child themes that you have. In my case the problem was caused by the function.php of the child theme.

    Hope it helps someone.

    Hi @ciltocruz,

    Thank you for the update and the tip about child themes.

    Thread Starter scruffy1

    (@scruffy1)

    Hi,

    We managed to catch these errors running WP 5.5 and latest Yoast (I redacted the website name), thanks Tracey

    Uncaught TypeError: o.dispatch(...) is null
    ????<anonymous> https://www.xxxxx.co.uk/wp-content/plugins/wordpress-seo/js/dist/post-edit-1481.js:1
    post-edit-1481.js:1:144435
    ????<anonymous> https://www.xxxxx.co.uk/wp-content/plugins/wordpress-seo/js/dist/post-edit-1481.js:1
    
    Uncaught TypeError: o.dispatch(...) is null
    ????<anonymous> https://www.xxxxxx.co.uk/wp-content/plugins/wordpress-seo/js/dist/post-edit-1481.js:1
    post-edit-1481.js:1:147997
    ????<anonymous> https://www.xxxxx.co.uk/wp-content/plugins/wordpress-seo/js/dist/post-edit-1481.js:1
    

    Hi @scruffy1,

    Thank you for troubleshooting this further and finding these Javascript errors.

    However, we can’t reproduce this error in a local test environment. To find the cause, we would still recommend doing a conflict check to find which combination of theme/plugins is causing this error which in turn makes Yoast failing to run.

    We know you can’t do much on the live site, but please know that when you use the troubleshooting mode of the Health Check plugin, this is only affecting your own logged in user and session. This does not affect any other user or site visitor while doing this testing.

    If that is still not possible, doing the Conflict Check on a staging site is another solution to do further troubleshooting.

    Thread Starter scruffy1

    (@scruffy1)

    Hello,

    Checked with site health, there were no issues all tests passed.

    By the way the site health / troubleshooter plugin you suggest has not yet been updated to be compatible with WP 5.5 and therefore I would be inclined to not trust the results.

    thanks Tracey

    • This reply was modified 4 years, 3 months ago by scruffy1.

    Hi @scruffy1,

    Thank you for your reply.

    Did you run a complete conflict check to check combinations of plugins and your theme? The diagnosis tests do only checks but don’t check on plugin/themes and how it loads on different pages.

    Doing a full conflict check with the troubleshooting mode, you can find the culprit. It would switch to a default twenty-X theme (if one is installed) and disables all plugins (as said before, only for your user). Then you can enable Yoast SEO and check if it loads on posts/pages. It probably will. Then you can switch to the theme that you are using and check again. If it then fails to load, you know that your theme has issues with WP 5.5. If Yoast SEO still loads, you can then continue to enable one plugin at a time and check again on each step to see if Yoast fails to load, when it does, you know what plugin is causing the Javascript errors which in turn makes Yoast SEO fail to load too.

    All of the above will only be affecting your own user, other users or site visitors will not be affecting while you are in troubleshooting mode. Hope this explains enough. We have a video and a step-by-step guide on this too, linked earlier: https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/.

    Thread Starter scruffy1

    (@scruffy1)

    Hi,

    OK. Using the plugin which is not up to date with WP 5.5, what we have found during the testing mode is – when using twenty theme toast works, when using the madras theme toast does not work. This I assume points to a theme issue.

    Thanks Tracey

    Hi @scruffy1,

    Thank you for investigating.

    Sounds like it yes. If you are running their latest version of the theme and have these issues, please contact the theme developers to get this investigated and solved. Thank you.

    Thread Starter scruffy1

    (@scruffy1)

    Hi,

    It is the Mediacentre theme from Madras Themes.

    We have been in touch with their developers and given them all the info we have.

    Thanks Tracey

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘14.8.1 still has jquery issue’ is closed to new replies.