WordPress Critical Error After Updating to 3.4.1

  • Resolved wardencenter

    (@wardencenter)


    1 year ago

    Greetings,

    After Updating to Hypercache 3.4.1, site is down with “There has been a critical error on this website. Learn more about troubleshooting WordPress.“

    Running: WP 6.3.2, Blocksy Theme 1.9.8 with Blocksy Companion 1.9.8

    Steps: Updated Hypercache to 3.4.1, goto Settings-Hypercache, “clean whole cache”.
    Also happens if goto Settings-Permalinks, save permalinks (with no changes), then Settings-Hypercache (don’t have chance to click on anything before error page appears).

    Both admin interface and website go down, showing just the error quoted.

    I restored from backup and all is fine again for me using Hypercache 3.4.0.

    FYI: I also went to an old backup and updated Hypercache with WP 6.3.1 and Blocksy 1.9.7 installed and received same error.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Stefano Lissa

    (@satollo)

    That’s a very bad news! A fatal error should have been logged in your server error logs, can you get them from your provider or cpanel?

    Plugin Author Stefano Lissa

    (@satollo)

    And usually WP send an email with the error details to the admin email address, the one set on WP main settings: did you receive something?

    Thread Starter wardencenter

    (@wardencenter)

    Ah-ha! I found the log in cPanel. Here it is (with our domain info removed):

    2023-10-28 11:36:24.565203 [NOTICE] [2197968] [T0] [207.46.13.111:59914:HTTP2-1#APVH_xxxxx.org:443] [STDERR] PHP Warning: gzopen(/home/xxxxx/public_html/siteres/wp-content/cache/hyper-cache/xxxxx.org/404-https.html.gz): Failed to open stream: No such file or directory in /home/xxxxxx/public_html/siteres/wp-content/plugins/hyper-cache/plugin.php on line 679\n

    Not sure if this is the only error log. Feel free to tell me where else to look. Also, I can say that the directory WAS indeed there, because I tried to recover from the error by renaming the hypercache folder in file editor (didn’t help).

    Thread Starter wardencenter

    (@wardencenter)

    Apologies – errors from “error_log” file:

    [28-Oct-2023 15:05:01 UTC] PHP Fatal error: Uncaught Error: Undefined constant “HC_MOBILE” in /home/xxxxx/public_html/siteres/wp-content/advanced-cache.php:19 Stack trace: #0 /home/xxxxx/public_html/siteres/wp-settings.php(96): include() #1 /home/xxxxx/public_html/siteres/wp-config.php(92): require_once(‘/home/xxxxx/…’) #2 /home/xxxxx/public_html/siteres/wp-load.php(50): require_once(‘/home/xxxxx/…’) #3 /home/xxxxx/public_html/siteres/wp-blog-header.php(13): require_once(‘/home/xxxxx/…’) #4 /home/xxxxx/public_html/index.php(17): require(‘/home/xxxxx/…’) #5 {main} thrown in /home/xxxxxx/public_html/siteres/wp-content/advanced-cache.php on line 19

    We’re running php 8.0

    Plugin Author Stefano Lissa

    (@satollo)

    Thank you very much, should be fixed on 3.4.2… there was a plan to remove the “mobile cache”, which has no more meaning today, and I made a mistake. I’ll remove it on next version!

    Thread Starter wardencenter

    (@wardencenter)

    You fixed it!!!

    Did a backup and tried again with 3.4.1 update and found the error only happened after clicking “clean whole cache”. BUT – I now see 3.4.2 – I updated and everything is working as expected.

    Well done!!

    Thread Starter wardencenter

    (@wardencenter)

    We love our Hypercache, btw! It always works and it’s the only cache plugin we’ve found that doesn’t slow down our site. Thank you!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WordPress Critical Error After Updating to 3.4.1’ is closed to new replies.