Support » Plugin: Yoast SEO » Error after 11.1 upgrade

  • Resolved OneMist8k

    (@onemist8k)


    Hello,

    Based on the reply of forum moderator Jan Dembowski (@jdembowski) who asked us to start a new topic to report this error instead of responding to the previous topic, I am doing so here.

    Like many others, I am receiving an error after upgrading to Yoast 11.1. No other plug-in was upgraded, the theme was not changed in any other way. This is a warning that appears above the nav bar. Changing out the logo from .svg to .png does not help, nor does having debug turned off (which it was already).

    The only thing that got rid of this error was turning off the Yoast plug-in.

    If you need any specific information about my configuration, please let me know and I’ll provide it.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support amboutwe

    (@amboutwe)

    With the limited information provided, I think the error has been reported here:

    https://github.com/Yoast/wordpress-seo/issues/12811

    If it’s a different error, please provide the full error (masking the server path is acceptable) and more information about the issue.

    Brandon Holcombe

    (@brandonhcreativemediacom)

    Also getting the Warning: Illegal string offset ‘width’ in and ‘height’ errors after 11.1 update. I should add that I don’t have the company logo or name fields set, they’re still blank, so the proposed fix linked to that doesn’t help.

    Where can we get a .zip with the v11.0 release so I can roll back? At present I can only roll back to v10 on my backup.

    • This reply was modified 4 months, 3 weeks ago by  ispreview.
    • This reply was modified 4 months, 3 weeks ago by  ispreview.

    Posting a “fix” to this error I found on another thread in this forum. It worked for me.

    With these lines in the WP_CONFIG file, the warnings no longer appear. For me, WP_DEBUG was already set to false, but the other three lines had to be added.

    ini_set(‘display_errors’,’Off’);
    ini_set(‘error_reporting’, E_ALL );
    define(‘WP_DEBUG’, false);
    define(‘WP_DEBUG_DISPLAY’, false);

    It’s not a fix, you’re just hiding a problem that still needs to be fixed. Personally I’m not a fan of this approach as you’re also hiding other potential future problems. It would be far better if they patched correctly or rolled back until it’s resolved as a lot of people will not be watching this forum, but will be getting the warning.

    Plugin Author Taco Verdonschot

    (@tacoverdo)

    @ispreview Please do notice there’s a huge difference between warnings, which are indications that something might break in the future but don’t affect script execution just yet, and errors, which indicate something is broken and affect script execution.

    Of course, it needs fixing. But rolling back the entire release, or issuing a patch release just to fix this warning doesn’t make sense.

    Fortunately, our development team just confirmed this will be in Yoast SEO 11.2 at the latest, which is the next scheduled release.

    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 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.