13.4 Errors

  • Resolved Studio Pence

    (@bpence)


    4 years, 7 months ago

    With the latest version of Yoast, getting errors in Console when trying to use the media library. This all goes away, and the media library works, when Yoast is deactivated.

    wp-auth-check.min.js?ver=5.3.2:1 Uncaught TypeError: Cannot read property 'hasClass' of undefined
    at HTMLDocument.<anonymous> (wp-auth-check.min.js?ver=5.3.2:1)
    at HTMLDocument.dispatch (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:3)
    at HTMLDocument.r.handle (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:3)
    at Object.trigger (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:3)
    at Object.a.event.trigger (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:8)
    at HTMLDocument.<anonymous> (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:3)
    at Function.each (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:2)
    at a.fn.init.each (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:2)
    at a.fn.init.trigger (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-resizable,jquery-ui-position,moxiejs,&load[chunk_1]=plupload,jquery-ui-sortable&ver=5.3.2:3)
    at Object.<anonymous> (heartbeat.min.js?ver=5.3.2:1)

    and:

    load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:43 Uncaught TypeError: _.pluck is not a function
    at wp.Backbone.Subviews.detach (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:43)
    at i.render (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:43)
    at initialize (media-grid.min.js?ver=5.3.2:1)
    at i.h.View (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:41)
    at i.constructor (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:43)
    at i.constructor (media-views.min.js?ver=5.3.2:1)
    at i [as constructor] (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:41)
    at i [as constructor] (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:41)
    at new i (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:41)
    at Object.wp.media (load-scripts.php?c=1&load[chunk_0]=hoverIntent,common,hoverintent-js,admin-bar,jquery-ui-draggable,jquery-ui-button,jquery-ui-dialog,underscore,shortcode,backbone,&load[chunk_1]=wp-util,wp-backbone,media-models,wp-plupload&ver=5.3.2:44)
Viewing 5 replies - 1 through 5 (of 5 total)

  • My site completely crashed after updating to 13.4. I get 503 errors when trying to access WordPress and my site throws a fatal error message when users attempt to access. Going into cPanel, it tells me that I/O Usage and Physical Memory Usage are maxed out. I was able to get in and delete Yoast SEO since that is the only change I’ve made and my site worked just fine. Tried reinstalling Yoast SEO and my site is once again crashing.

    Plugin Support devnihil

    (@devnihil)

    @bpence Can you please confirm you are using the most recent Yoast v13.4.1? You can learn more about updating here: https://kb.yoast.com/kb/how-can-i-update-my-free-plugin/

    Can you confirm you are using WordPress 5.4? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/
    ?
    ?If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?

    If the issue is still occurring after confirming both Yoast SEO and WordPress are updated, this may be due to a plugin or theme conflict. Can you try and gather as much information for us as possible? Please perform the following:

    1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
    2. Check for conflicts.
    3. Check for JavaScript errors with your console.
    If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers. Please report the issue to a third party developer as well.

    If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.

    @krystianya Please create a new issue if you are experiencing a similar problem as this helps us in tracking as this can be caused by many different variables (WordPress version, other plugins, etc).

    Plugin Support devnihil

    (@devnihil)

    @bpence Can you please confirm you are using the most recent Yoast v13.4.1? You can learn more about updating here: https://kb.yoast.com/kb/how-can-i-update-my-free-plugin/

    Can you confirm you are using WordPress 5.4? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/
    ?
    ?If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?

    If the issue is still occurring after confirming both Yoast SEO and WordPress are updated, this may be due to a plugin or theme conflict. Can you try and gather as much information for us as possible? Please perform the following:

    1. Make sure the issue doesn’t persist when Yoast SEO is disabled.
    2. Check for conflicts.
    3. Check for JavaScript errors with your console.
    If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers. Please report the issue to a third party developer as well.

    If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.

    @krystianya Please create a new issue if you are experiencing a similar problem as this helps us in tracking as this can be caused by many different variables (WordPress version, other plugins, etc).

    Plugin Support Jerlyn

    (@jerparx)

    Closed due to inactivity.

    Thread Starter Studio Pence

    (@bpence)

    @jerparx – thank you. We determined the issue was caused by a plugin conflict and have since fixed it!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘13.4 Errors’ is closed to new replies.