Console Warning in WP BackEnd concerning Yoast plugin

  • Resolved jtcheng

    (@jtcheng)


    4 years, 9 months ago

    To Whom It May Concern,

    I’ve been noticing in the browser console that whenever I go to the WordPress Dashboard on the admin page or backend, I always see this warning:

    The resource https://yoast.com/app/themes/yoast-theme/fonts/FontAwesome.woff2 was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it has an appropriate as value and it is preloaded intentionally.
    The resource https://yoast.com/app/themes/yoast-theme/css/fontawesome.min.css?ver=1585315602 was preloaded using link preload but not used within a few seconds from the window’s load event. Please make sure it has an appropriate as value and it is preloaded intentionally.

    I’ve been noticing this for quite a while and I suspect it started popping up on one of the updates and/or on a wordpress core update (can’t be totally sure).

    But do you guys know what this means and whether there is something about the plugin that needs to be addressed?

    Thanks

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hello @jtcheng!

    Does it go away if you deactivate Yoast SEO? Also, what version of WordPress and Yoast SEO are you running? Can you please make sure they’re updated? The latest version of the Yoast plugin is 14.4.1.

    Thread Starter jtcheng

    (@jtcheng)

    Hi,

    I am using version 14.3 on the production site, but I have used 14.4.1 and this warning still persists.

    When the plugin is deactivated, the warning goes away.

    I am hesitant to update to version 14.4.1 given that it throws a new warning:
    wp-seo-post-scraper-1441.js?ver=14.4.1:1 Marking links with nofollow/sponsored has been disabled for WordPress installs < 5.4. Please upgrade your WordPress version or install the Gutenberg plugin to get this Yoast SEO feature.

    And since I’m using WordPress 5.4.2 and I don’t intend to use Gutenberg, it seems like the issues are compounding, which is why I’m hoping the issues are resolved before considering updating and seeing if I want to take on more features (and potentially problems).

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi,

    Thanks for confirming that this issue occurs with WordPress 5.4.2 and Yoast SEO for WordPress 14.4.1.

    We’re sorry that you are experiencing problems that might be caused by our plugin!

    Just to be sure, 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.

    Thread Starter jtcheng

    (@jtcheng)

    Hi,

    I have utilized a staging site and backed up the database.

    Then, I proceeded to disable all plugins except Yoast SEO and switched to the 2019 theme.

    The warning still persists on the dashboard in wp-admin so I’m quite sure this is something going on with the plugin at this point.

    Thread Starter jtcheng

    (@jtcheng)

    Follow up.

    While I was doing this exercise, I also noticed this other warning:
    A cookie associated with a cross-site resource at https://yoast.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

    I’ve seen similar warnings come and go with other plugins. Any effort to address this on Yoast’s end?

    Thanks

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    Thanks for bringing this to our attention. We were able to reproduce the issue on our end.

    Therefore, we’d like you to please submit a proper bug report directly at the Github development repository so our development team can look into this issue further.

    We appreciate your effort on this.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Console Warning in WP BackEnd concerning Yoast plugin’ is closed to new replies.

Tags