• Resolved puregraphx

    (@puregraphx)


    We just updated Yoast to 5.8 and now we see this error on the fronted. When we disable the plugin, the site loads ok.

    Fatal error: Uncaught Error: Call to undefined method RYSC::head_product_name() in /home/doublemp/public_html/dev/wp-content/plugins/remove-yoast-seo-comments/remove-yoast-seo-comments.php(110) : eval()’d code:17 Stack trace: #0 /home/doublemp/public_html/dev/wp-content/plugins/remove-yoast-seo-comments/remove-yoast-seo-comments.php(110): eval() #1 /home/doublemp/public_html/dev/wp-includes/class-wp-hook.php(298): RYSC->rewrite(”) #2 /home/doublemp/public_html/dev/wp-includes/class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array) #3 /home/doublemp/public_html/dev/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #4 /home/doublemp/public_html/dev/wp-includes/general-template.php(2589): do_action(‘wp_head’) #5 /home/doublemp/public_html/dev/wp-content/themes/Avada/header.php(22): wp_head() #6 /home/doublemp/public_html/dev/wp-includes/template.php(688): require_once(‘/home/doublemp/…’) #7 /home/doublemp/public_html/dev/wp-includes/template.php(647): load_template(‘/home/doublemp/…’, true) #8 /home/doublemp/pu in /home/doublemp/public_html/dev/wp-content/plugins/remove-yoast-seo-comments/remove-yoast-seo-comments.php(110) : eval()’d code on line 17

Viewing 12 replies - 16 through 27 (of 27 total)
  • ondrej7

    (@ondrej7)

    If you need fast fix with “Yoast comments removed” – it means you don’t want YOAST comments in your page source, try this to put following code in file functions.php (you can access this file from Appearance->Editor and select file functions.php to edit). It will remove all comments sections from HTML.
    Put it AT THE END of functions.php
    ———————————————————————

    function callback($buffer) {
    //any line beginning with “<!– ” (there is a space after dashes)
    $buffer = preg_replace(‘/<!–\s.*–>/’, ”, $buffer);
    return $buffer;
    }
    function buffer_start() {
    ob_start(“callback”);
    }
    function buffer_end() {
    ob_end_flush();
    }
    add_action(‘get_header’, ‘buffer_start’);
    add_action(‘wp_footer’, ‘buffer_end’);

    • This reply was modified 7 years ago by ondrej7.
    • This reply was modified 7 years ago by ondrej7.
    • This reply was modified 7 years ago by ondrej7.
    shap2zj

    (@shap2zj)

    No need to delete either plugin.
    Just download Yoast 5.7.1 zip file and install yourself and use both plugin together.
    The Yoast’s Github release page is as follow:
    https://github.com/Yoast/wordpress-seo/releases

    Jim McClain

    (@enterprisejm)

    Or… deactivate RYSC temporarily and be patient. Let the Remove Yoast SEO Comments plugin author update the plugin as soon as possible. Monitor your dashboard and you’ll be notified of the update when it’s available. Then you can reactivate it.

    Joost de Valk

    (@joostdevalk)

    Hey everyone, sorry to see so many people get fatals because of this issue!

    Let me be clear on the Yoast policy here:

    We didn’t do this on purpose, nor do we make removing this comment very hard to do. We’re not hiding anything, this is just a method in a class. The comment is actually used in our code, the force rewrite functionality depends on it.

    What we do though, which caused this fatal, is continue to develop our plugin. Sometimes we refactor our code to make it performant and/or easier to maintain. The author of this plugin did not code defensively, he should make his code simply not fatal when we change our code.

    Unfortunately, this is not the first time this plugin has caused fatal errors, so our advice is simply not to run this plugin. The comment doesn’t hurt anybody, other than that it helps us gather some stats on how many sites use Yoast SEO. If you want to remove all comments from the frontend, there are certainly better plugins to do that, simply use a plugin to minify all the output.

    dekket

    (@dekket)

    @ut4utc
    That is LITERALLY what everyone in this entire thread, has already said. So GTFO with your spammy links.

    dekket

    (@dekket)

    @joostdevalk

    The comment doesn’t hurt anybody, other than that it helps us gather some stats on how many sites use Yoast SEO.

    This can not be more than partially true.
    If all you wanted was to gather stats, you could do that with an innocuous comment like <!– y02394842984 –> or something else totally unique.

    Also, if the comment truly does not do anything but provide stats, a setting to remove all Yoast comments would exist.

    Truth is, you want the advertising. Which is fine, but don’t act like it’s for other reasons.

    @dekket
    Where is spam in my links? in my link I shared with the solution of the problem and only.

    Thread Starter puregraphx

    (@puregraphx)

    @ut4utc the solution was already posted here multiple times, you are just desperate to get some traffic to your blog. Added value? 0.

    Joost de Valk

    (@joostdevalk)

    @dekket if you think it’s “advertising”, you don’t understand how most WordPress users (not developers) find their plugins. With over 7.5 million installs of Yoast SEO, I can honestly say it’s not the comment in the source code that got us there.

    The comment is helpful because it makes it easy to establish which version of the plugin (both free / premium and actual version #) someone is using. That’s helpful to our support team in many, many cases. On top of that, sites like builtwith use it to generate stats on our plugin. That’s why it’s there.

    If we made it something “innocuous”, nobody would get why it’s there. And that freaks more people out than you think.

    @puregraphx
    sorry for my bug. I can’t know fluent english. I read only two last comment, that users say that has problem and I wrote article for me and for them. BI can’t need more traffic in my site, because i write articles 1-2 times in month and not need that my blog be same as facebook, my blog only for me, this is my datebase LOL

    Plugin Author Mitch

    (@lowest)

    Hello all.

    Thank you for reporting this issue to me. Unfortunately, I don’t have the time to check the support page every day.

    The issue has been fixed. Special thanks to Yoast SEO for changing this specific piece of code we rely on, it motivates me to keep updating this plugin.

    As mentioned in the FAQ, it’s certainly recommended to run a test installation of WordPress with Yoast SEO and RYSC to see if something breaks in new updates. I cannot prevent this from happening.

    I apologize for the late response.

    – Mitch

    katyloris567890

    (@katyloris567890)

    Hey, there i am facing some problems by the latest version 5.8 of Yoast SEO with my website. Same problem as above mentioned above.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘Plugin conflict with Yoast 5.8’ is closed to new replies.