'THERE HAS BEEN A CRITICAL ERROR ON THIS WEBSITE' AFTER A BULK PLUGIN UPDATE

phppluginswordpress88 replies · 1.5K views · started
  1. ehh respectfully disagree, i tried that and it made plugin worse, bump... still happening with wordpress for me

    32 4 helpful
  2. To disable all plugins without the dahsboard, rename wp-content/plugins to plugins-off over FTP or the hosts file manager. WordPress deactivates everything it cant find. If the site comes back, renmae teh folder back and then rename individual plugin folders one by one to find the culprit.

    7 6 helpful
  3. been there man pro tip: write down what u change. i didnt and had to redo wordpress from scratch. following, hvaing the same problem hope that helps :)

    thumbsup

    2 3 helpful
  4. If the theme is the problem, rename the active theme's folder in wp-content/themes. wordPress falls back to a default theme if one is installed. or run wp theme activate with a default theme name via WP-CLI.

    1 2 helpful
  5. pro tip: write down what u change. i didnt and had to redo wodrpress from scratch lmk how it goes

    0 1 helpful
  6. ok so bump... still happening with php for me

    7 0 helpful
  7. ahh classic try turning off teh fan curve first, fixed it for me hope that helps :)

    2 0 helpful
  8. hmmm honestly just reset teh antivirus and save yourself teh pain

    2 2 helpful
  9. pro tip: write down what u change... i didnt and had to redo update from scratch

    2 0 helpful
  10. so annoyed rn i swear wordpress is cursed

    2 1 helpful
  11. hmmm going forward: disable auto-updates for big plugins like page builders and e-commerce add-ons, update them on staging first, and keep a backup u've actually tested restoring. Many hosts offer one-click staging for exactly this.

    5 6 helpful
  12. oof with SSH and WP-CLI its quicker: wp plugin deactivate --all --skip-plugins --skip-themes to recover, then wp plugin activate name one at a time. wp plugin list shows versions so u can spot what updated recently. lmk how it goes

    2 0 helpful
  13. following, having the same problem. try turning off the default config first, fixed it for me lmk how it goes

    15 0 helpful
  14. ok so ok this thread just saved my weekend. wait does this also apply to wordpress? pls help 🙏

    9 0 helpful

Reply to this topic

Sign in or create an account to reply.