• Resolved sharemyyear

    (@sharemyyear)


    I’ve been advised by Pipdig that the Yoast plugin is causing the following error on my site

    Fatal error: ob_start(): Cannot use output buffering in output buffering display handlers in /home2/sharemyyear/public_html/sharemyyear.co.uk/wp-content/plugins/wordpress-seo/frontend/class-frontend.php on line 1820

    This occurs when I try and use the menus on my site https://sharemyyear.co.uk and stops when I deactivate Yoast.

    Is there a fix for it or do I need to simply deactivate Yoast and use something else?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter sharemyyear

    (@sharemyyear)

    Are there any kind of admins who review these posts? Otherwise I imagine this post falls down the board and doesn’t get seen

    Plugin Support Michael Tiña

    (@mikes41720)

    Are you using WordPress 4.9.8 and Yoast SEO for WordPress 8.3?

    Does clearing your caching from your plugin, theme, server, browser, or CDN such as Cloudflare resolve the issue? If you are not sure how to clear your server caching, please speak with your host provider. If you need to clear your browser caching this guide may help — https://kb.yoast.com/kb/how-to-clear-my-browsers-cache/

    If that doesn’t help resolve the issue, can you try and gather as much information for us as possible and perform a conflict check? 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.

    Thread Starter sharemyyear

    (@sharemyyear)

    Thanks for your reply but a lot of this sounds like it is for someone more advanced than me. I use a simple plug and play system.

    I’ve tried loading my site in a different browser, the problem is still there. As soon as I deactivate Yoast, the problem is no longer there. With my non-technical mind, this suggests that the issue is in fact Yoast

    I have the exact same issue and no one replied to me. It occurs when only the yoast plugin is active, so it’s not a conflict error. Clearing all the caches does not resolve the error. We are using the latest software versions and there are no javascript errors.

    As it is not a site specific error it does not seem fair that you would only give a fix to premium customers.

    The same error has been reported in this thread and it turned out to be a conflict with another SEO plugin when a conflict check was performed. Since we could not confirm and determine what the issue is only by knowing that the error shows up when the plugin is activated, we suggest doing a conflict check as well to know what other plugin is conflicting with Yoast SEO.

    How can it be a conflict when the problem happens with only the Yoast plugin activated?

    Plugin Support Michael Tiña

    (@mikes41720)

    Again, this is why we advise for a conflict check. Do you have a custom theme? If you’ve disabled all of your non-Yoast plugins and use a default theme like TwentySeventeen, does the issue still occur? If the issue resolves itself and the fatal error doesn’t appear anymore, it might be a conflict with your chosen theme.

    • This reply was modified 7 years, 8 months ago by Michael Tiña.
    Plugin Support Michael Tiña

    (@mikes41720)

    No further response, setting to resolved.

    Thread Starter sharemyyear

    (@sharemyyear)

    NOT RESOLVED! Just to be very clear, it feels like the preferred solution here is that we pay for your premium solution so that you will fix a problem with your standard product? Maybe we just need to move to a product that works…

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

The topic ‘Error message when trying to view menus’ is closed to new replies.