Viewing 13 replies - 46 through 58 (of 58 total)
  • @msteel Sounds like a whole different issue. Do you use the WordPress installer for installing and updating plugins or do you use another method?

    msteel

    (@msteelnapcocom)

    WP installer. I also got a message that a different class was missing, this is the same error I’d been experiencing. Maybe WPSEO_Updater or something? I removed the plugin folder, went to plugins page to de-activate. Place back in the folder, refresh plugins page, reactivate the plugin and that has always resolved the first error.

    This error remains fatal until I comment it out.

    @msteel please create a separate issue for this (preferrably a bug report on GitHub), since it’s definitely not related to this topic.

    The patch (2.3.1) for the wp_query fatal has been released. We’ve received positive feedback on it from multiple users. Marking this topic as resolved.

    Thanks @all for your input and cooporation.

    msteel

    (@msteelnapcocom)

    Already done. Thanks.

    This is INSANE. You’ve been using your most loyal users as BETA testers for years. I’ve had enough. My site got nerfed this morning with the update and the solution? DELETE Yoast SEO via FTP.

    @kidflash Solution is update.
    But although i share your frustration re us being beta testers, given so many users of this plugin, and so many plugins,themes, in use worldwide, you will always get some issues. Mine all worked fine without this latest updated update.

    Best leave updates for a week, let the bugs get sorted.

    The only reason I updated this morning was after I got an e-mail from Yoast asking me to extend/update to PREMIUM.

    So the plugin they were asking me to pay for was going to nerf my site? Totally unprofessional.

    No more free passes for these jokers.

    It’s time to let everyone know how these guys operate.

    I’m with @mrppp . Yes it’s frustrating when releases result in bugs for some users. But as we know this we can either update and work with the plugin authors to resolve any issues that may arise, or wait a week or so for any issues to be ironed out.

    The plugin remains excellent in its functionality, and I can live with a little care over updating every month or so.

    I see this has been marked as resolved by the developer…is it really? Seems to still be a lot of questions, to so quickly right this issue off?

    As a business owner that doesn’t have the depth of experience and coding skills like many on this page, it is particularly difficult (and painful) to be the guinea pig for beta testing something like this. I think the developers have lost sight of the fact that not everyone using their product are experts.

    Does anyone know, if I get rid of the Yoast plug-in and switch to another, what happens to all the SEO info that we’ve created for the 1,000-plus articles on our site?

    The new update seems to have fixed the problem for me, although this new search console tab is pretty useless for free users… since you really can’t do anything with it unless you upgrade.

    same issue 2.3.1 is causing same issue.

    itsat

    (@itsat)

    Same problem and I would like to delete or reinstall but HOW has anyone managed to get into the administrative panel. That’s my problem.
    The updates caused the problem and WordPress messes everything up with updates.
    All I get is that fatal error line that doesn’t allow me to get into wordpress to be able to uninstall these defective updates.

    Please, someone help. Very frustrating. Thank you

    this is the line I get:
    Fatal error: Call to undefined method Yoast_Api_Libs::load_api_libraries() in /home/content/n/a/t/nat2004/html/blog/wp-content/plugins/google-analytics-for-wordpress/admin/class-admin.php on line 42

    AskKim

    (@askkim)

    Hi itsat,

    To do this, you will need access to your website’s filesystem through your webhosting control panels file manager, FTP etc.

    Follow these steps:

    Navigate to where your site is in the file system.
    Navigate to /wp-content/plugins
    Find the directory/folder of the plugin causing the problem
    Rename the directory to something else (i.e. badplugin-disabled)
    You should now be able to login to WordPress, and you will receive a small error message indicating that the plugin failed to load.

Viewing 13 replies - 46 through 58 (of 58 total)
  • The topic ‘Heads up..Latest udpate today killed site.’ is closed to new replies.