Sign in

my wordpress died after bumping the php version. the debug log had a surprise

Solvedphppluginswordpress27 replies · 299 views · started
Reply
  1. Noah Yilmaz
    @noah_cron

    Developer here, but WordPress isnt my daily thing. A clients site broke after bumping the PHP version:

    There has been a critical error on this website.

    There has been a critical error on this website.
Learn more about troubleshooting WordPress.

    The classic critical error page. Their setup has around twenty plugins including a forms plugin, i want to find teh exact cause instead of randomly deactivating things and hoping. Whats the fastest way to see the real PHP error?? Happy to post logs or the plugin list if that helps narrow it down. pls help 🙏

    thinking

    12
  2. Rhea Fontaine
    @daemon_bench

    ok so if it started after a PHP version change, an older plugin or theme may use functions removed in newer PHP. the debug log will show something like Call to undefined function. switch PHP back temporarily in the hosts control panel, then update or replace teh incompatible plugin before upgrading PHP again. fingers crossed 🤞

    1 0 helpful
  3. Elena J.
    @elena_frame

    dumb question but how do i even check teh firmware. told my boss it would take 10 minutes. its been a whole week ??

    1 11 helpful
  4. Rhea Fontaine
    @daemon_bench

    ok so ok this thread just saved my weekend. pro tip: write down what u change. i didnt and had to redo forms from scratch

    2 0 helpful
  5. Esme N.
    @esmen539

    With SSH and WP-CLI it's quicker: wp plugin deactivate --all --skip-plugins --skip-themes to recover, then wp plugin activate name one at a time lmao wp plugin list shows versions sooo you can spot what updated recnetly. fingers crossed 🤞

    0 1 helpful
  6. Elena J.
    @elena_frame

    oh ive been there lol came here to say exactly this fingers crossed 🤞

    5 3 helpful
  7. Jonas
    @cron_hound-10k

    following, having the same problem

    thumbsup

    3 2 helpful
  8. Jonas
    @cron_hound-10k

    oof to disable all plugins without the dashboard, rename wp-content/plugins to plugins-off over FTP or the hosts file manager. WordPress deactivates everything it cant find. If teh site comes back, rename the folder back and then renmae individual plugin folders one by one to find the culprit. good luck man!

    thinking

    1 2 helpful
  9. Rhea Fontaine
    @daemon_bench

    oof if the theme is the problem, rename the active themes 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.

    3 4 helpful
  10. Jonas
    @cron_hound-10k

    try turning off teh router first, fixed it for me, ok this thread just saved my weekend good luck man!

    4 1 helpful
  12. Ash
    @abauer

    btw unrelated but anyone elses coffee machine also judging them today. is version even worth bothering with or should i just leave it

    1 0 helpful
  13. Rhea Fontaine
    @daemon_bench

    oh ive been there lol turn on logging to see the actual error, in wp-config.php, above the line that says to stop editing, add define('WP_DEBUG', true);, define('WP_DEBUG_LOG', true); and define('WP_DEBUG_DISPLAY', false);. Reload teh site, then read wp-content/debug.log. The fatal error line names the file, which tells u which plugin or theme is responsible.

    13 0 helpful
  14. Esme N.
    @esmen539

    btw i come back to this thread every week just for teh drama

    8 5 helpful
  15. Elena J.
    @elena_frame

    try turning off the DNS first, fixed it for me

    1 0 helpful
  16. Jonas
    @cron_hound-10k

    @daemon_bench what did u end up doing in teh end 🤷 pro tip: write down what u cahnge, i didnt and had to redo forms from scratch

    6 1 helpful
  17. Jonas
    @cron_hound-10k

    pro tip: write down what u change. i didnt and had to redo php from scratch worked for me anyway 🤷

    4 1 helpful
  18. Silas Ziegler
    @mutex_monk

    lol same thing happened to me following, having the same problem... honestly just reset the firmware and save yourself the pain

    lol

    0 2 helpful
  20. Esme N.
    @esmen539

    this. sooo much this. for me it was the fan curve. swapped it and boom, fixed

    16 0 helpful

Reply to this topic

Sign in or create an account to reply.