Support » Plugin: Yoast SEO » Yoast SEO conflict with Gutenberg

  • Resolved carloscastilloadhoc

    (@carloscastilloadhoc)


    Good morning.

    Several weeks ago we noticed in one of the webpages we manage an error would show up in the backend while creating/editing posts using the post editor Gutenberg, the error is the following one:

    Warning: count(): Parameter must be an array or an object that implements Countable in /home/******/public_html/wp-includes/post-template.php on line 317

    Checking what was updated at the time of the error, we realized it was the Yoast SEO plugin causing it, this is the data we have gathered so far:

    1) It only happens with the Gutenberg editor.
    2) Rolling back to version 13.5 fixes the error, as of today, version 14.1 still causes it.
    3) We have PHP 7.3.16 running in the server.
    4) WordPress is up to date (5.4.1.)

    Could you take a look at this? Thanks in advance.

Viewing 14 replies - 1 through 14 (of 14 total)
  • gary-SA

    (@garysharpahead)

    Yes there’s definitely a conflict occurring again with Yoast and Gutenberg.

    We’re experiencing the dreaded THIS BLOCK HAS ENCOUNTERED AN ERROR AND CANNOT BE PREVIEWED error message when trying to edit posts.

    Everything works again when Yoast is deactivated.

    WordPress 5.4.1 running and Yoast plugin up-to-date.

    Plugin Support Michael Tina

    (@mikes41720)

    Hello @carloscastilloadhoc and @garysharpahead

    Just to clarify, you have WordPress 5.4.1 and are utilizing the Gutenberg plugin 8.1.0? If you temporarily deactivate the Gutenberg plugin, you should still be using the Block Editor since you are using WordPress 5.0 and up. Could you then please check if the issue still occurs when you try to edit a post or page along with v14.1 of Yoast SEO?

    Thread Starter carloscastilloadhoc

    (@carloscastilloadhoc)

    Good morning.

    We are not using the Gutenberg separated plugin, but the integrated editor with WP 5.0+

    Kind regards.

    gary-SA

    (@garysharpahead)

    Morning Michael,

    We’re not using the Gutenberg plugin either, just the integrated blocks editor.

    Thanks

    Gary

    Plugin Support devnihil

    (@devnihil)

    @garysharpahead @carloscastilloadhoc Can you confirm you are using WordPress 5.4.1? 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/

    In order to run the current version of the Yoast SEO plugin it requires that WordPress either be version 5.4 or 5.3 so to run the plugin you would need to upgrade WordPress to one of those version. We also have more information on this here: https://yoast.com/supporting-older-versions-of-wordpress/

    ​If you update to the most current version of WordPress, 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. Check for conflicts.
    2. 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.

    gary-SA

    (@garysharpahead)

    Hi @devnihil,

    We’ve been running Yoast version 14.2 and WordPress core version 5.4.1 already so it’s not an outdated version issue.

    Seems no other plugins are conflicting and creating the problem for us, just Yoast. As soon as we deactivate Yoast the error of not being able to edit posts using the built in Gutenberg blocks goes away and we can happily edit again.

    Currently we’re having to deactivate Yoast to make or edit posts and then switch it back on, which obviously isn’t ideal.

    There doesn’t seem to be any Yoast related console errors.

    Many thanks,

    Gary

    Plugin Support Jeroen Rotty

    (@jeroenrotty)

    Hi @garysharpahead,

    Thank you for hooking in and replying.

    We tried replicating this while editing posts or pages on an installation where Yoast SEO is the only active plugin (14.2) and WordPress 5.4.1, but can’t replicate any of these issues. Have you run a conflict check with the health check plugin to see if any other active plugin is interfering with our plugin/the editor?

    In the troubleshooting mode that plugin provides, it temporarily deactivates all plugins and switches to a default theme without interfering with other site visitors or users. In this mode, please activate only Yoast SEO and see if you can replicate the issue. If you can still reproduce this issue, we ask you kindly to create a bug report on our Github repository with as much information as you can so our developers can have a look.

    If you can’t reproduce, switch back to the theme you were using and check again if the issues reappear. If so, the theme is the culprit. If it continues to work, then activate one plugin at a time and check when the issue reappears, then you know what plugin is causing the conflict.

    gary-SA

    (@garysharpahead)

    Hi,

    Thanks for the advice.

    In troubleshooting mode using the default WP theme I found that 2 plugins are conflicting with Yoast. Advanced Custom Fields Pro (which is a biggy) and a plugin called Slideshow.

    Not really sure what to do now though as ACF is used site wide.

    Any ideas? And can this be replicated on your end?

    Many thanks,

    Gary

    Plugin Support Priscilla Chapman

    (@priscillamc)

    Hi Gary,

    Does the problem still happen if you install and activate the ACF Content Analysis for Yoast SEO plugin?

    If you find that there’s a conflict with either of these plugins, you’re welcome to create a new GitHub issue for our developers here: https://github.com/Yoast/wordpress-seo/issues/. Please report the issue to the third-party developer as well.

    gary-SA

    (@garysharpahead)

    Hi Priscila,

    Yes unfortunately it does still occur.

    Thanks I’ll create a github issue now.

    Gary

    Plugin Support devnihil

    (@devnihil)

    @garysharpahead Thanks for confirming.

    @carloscastilloadhoc Were you able to confirm whether the issue still occurs when using version 14.2 of Yoast SEO and the ACF Content Analysis for Yoast SEO plugin?

    Thread Starter carloscastilloadhoc

    (@carloscastilloadhoc)

    Good morning. I haven’t been able to perform the tests yet, I expect to do it during this week and will update you with the results. Thanks.

    Plugin Support devnihil

    (@devnihil)

    @carloscastilloadhoc Thanks for the update, we’ll leave the post active and await your reply.

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Yoast SEO conflict with Gutenberg’ is closed to new replies.