Support » Plugin: Yoast SEO » 14.5 breaks the head

  • Resolved 2046

    (@o-o)


    while running latest WP and the latest Yoast with wp_debug false
    the head is broken.. and site end up as html without any scripts and such.

    [08-Jul-2020 16:30:04 UTC] PHP Notice:  is_feed was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in ./wp-includes/functions.php on line 5167
    [08-Jul-2020 16:30:04 UTC] PHP Notice:  is_single was called <strong>incorrectly</strong>. Conditional query tags do not work before the query is run. Before then, they always return false. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in ./wp-includes/functions.php on line 5167
    ./wp-content/plugins/wordpress-seo/src/integrations/front-end/handle-404.php:		if ( ! $this->is_feed_404() ) {
    ./wp-content/plugins/wordpress-seo/src/integrations/front-end/handle-404.php:	protected function is_feed_404() {
    ./wp-content/plugins/wordpress-seo/src/integrations/front-end/handle-404.php:		if ( ! \is_feed() ) {
    ./wp-content/plugins/wordpress-seo/src/integrations/front-end/handle-404.php:		$wp_query->is_feed = false;
    ./wp-content/plugins/wordpress-seo/src/integrations/front-end/rss-footer-embed.php:		if ( ! \is_feed() ) {

    the Yoast plugin deactivation returns all back to normal.

    note: The error is not visible when the wp_debug is set to true.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Carl B

    (@devnihil)

    @o-o Unfortunately we aren’t able to replicate this error.

    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.

    The error is not a javascript error as there is not css nor javascript as the head is blown away, the HTML head is basically non existent.

    I have deactivated almost all plugins except Timber as that is crucial dependency for the template. While activating all the plugins back all went ok, unless I turned o the Yoast. Then the page head was cut off.

    Plugin Support Rumejan

    (@onlyincebu)

    Hello @o-o!

    To check for conflicts, you need 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.

    You may follow the steps here: https://yoast.com/help/how-to-check-for-plugin-conflicts/

    edited:

    I see now {{ wp_head }} is the breaking point or in other code {{ function(‘wp_head’) }}

    still not resolved, the head is of only with wp_debug off

    • This reply was modified 4 months, 2 weeks ago by 2046.
    • This reply was modified 4 months, 2 weeks ago by 2046.
    • This reply was modified 4 months, 2 weeks ago by 2046.

    One news here.. I installed the All In One SEO Pack and that does not produce this bug.

    Same to me, when plugin folder is renamed, there is no problem. When wp-config’s WP_DEBUG is set to true, there is no problem. Otherwise I have a WordPress critical error notice.
    It’s got nothing to do with other plugins or theme, I have tested that.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.