Update crashes site – again

  • zimbo000

    (@zimbo000)


    3 days, 6 hours ago

    Five months after this, https://wordpress.org/support/topic/update-crashes-site-6/, and another update crash two months later, and re-installing from scratch as recommended at the time, the update from 3.24.0 to 4.0.3 crashed the site again. This time, it really did crash the site, I could not login unless I used the link in the WordPress error email. I de-activated the plugin once in, then re-activated it and all is OK. The update also crashed the sub-domain site as well. Seems like you guys have some serious problems somewhere…

    WordPress version 6.9.4
    Active theme: Enfold Child (version 1.0) Current plugin: Smush (version 4.0.3) PHP version 8.3.30 Error Details

    An error of type E_ERROR was caused in line 126 of the file /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/core/class-modules.php. Error message: Uncaught Error: Class “Smush\Core\Modules\Resize_Detection” not found in /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/core/class-modules.php:126
    Stack trace: 0 /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/core/class-modules.php(115): Smush\Core\Modules->__construct() 1 /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/core/class-core.php(157): Smush\Core\Modules::get_instance() 2 /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/core/class-stats.php(104): Smush\Core\Core->init() 3 /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/wp-smush.php(396): Smush\Core\Stats->__construct() 4 /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/wp-smush.php(286): WP_Smush->init() 5 /home/storage/322/4077322/user/htdocs/dev/wp-content/plugins/wp-smushit/wp-smush.php(255): WP_Smush->__construct() 6 /home/storage/322/4077322/user/htdocs/dev/wp-includes/class-wp-hook.php(341): WP_Smush::get_instance(”) 7 /home/storage/322/4077322/user/htdocs/dev/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array) 8 /home/storage/322/4077322/user/htdocs/dev/wp-includes/plugin.php(522): WP_Hook->do_action(Array) 9 /home/storage/322/4077322/user/htdocs/dev/wp-settings.php(593): do_action(‘plugins_loaded’) #10 /home/storage/322/4077322/user/htdocs/dev/wp-config.php(89): require_once(‘/home/storage/3…’) 11 /home/storage/322/4077322/user/htdocs/dev/wp-load.php(50): require_once(‘/home/storage/3…’) 12 /home/storage/322/4077322/user/htdocs/dev/wp-admin/admin.php(35): require_once(‘/home/storage/3…’) 13 /home/storage/322/4077322/user/htdocs/dev/wp-admin/update-core.php(10): require_once(‘/home/storage/3…’) 14 {main}

    thrown

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Hassan Akhtar

    (@khaxan)

    3 days, 6 hours ago

    Hi there, the class Resize_Detection is not being referenced/used in the code of version 4. What action did you perform on the site that caused this error? Is it still happening?

    Thread Starter zimbo000

    (@zimbo000)

    3 days, 5 hours ago

    Smush was listed under WordPress Updates like this:

    Smush

    You have version 3.23.4 installed. Update to 4.0.3. View version 4.0.3 details.
    Compatibility with WordPress 6.9.4: 100% (according to its author)

    I ticked its box and clicked the Update Plugins box. Update Plugins page displayed whilst the update started, then the site crashed and displayed thhe WordPress “your site is experiencing a critical error” page (or something similar).

    The WordPress error email had these lines in:

    In this case, WordPress caught an error with one of your plugins, Smush.

    First, visit your website (https://www.thehenleysociety.org/) and check for any visible issues. Next, visit the page where the error was caught (https://www.thehenleysociety.org/wp-admin/update-core.php?action=do-plugin-upgrade&_wpo_purge=51712621e2) and check for any visible issues.

    Plugin Support Saurabh – WPMU DEV Support

    (@wpmudev-support7)

    2 days, 12 hours ago

    Hello @zimbo000

    Hope you’re doing well today! I am sorry to hear about the issue you’re facing.

    I tried to replicate the issue on my lab site by installing the Smmush v3.23.4 and updating the plugin to the latest version 4.03. However, I was unable to replicate the fatal error you’ve shared.

    This could mean the issue is specific to the site and needs further investigation. Could you please confirm if you are still noticing the issue? Or was it not replicated again after deactivating and reactivating the plugin?

    To understand the environment better, could you please share the information from WP Admin Dashboard >> Tools >> Site Health >> Info tab? Ref: https://monosnap.ai/file/v01XpYJeeStmyU4C1fr0lBXoTS2BqO

    You can copy the information and share it via Google Drive or Pastebin.com

    If you wish to share it privately, you can email is at: wpsupport@incsub.com

    Subject: ATTN: WPMU DEV support – wp.org

    Please send:
    – Link to the site info
    – Link back to this thread for reference (https://wordpress.org/support/topic/topic-title/)
    – Any other relevant URLs/info

    To ensure we don’t miss your email, please let us know here once you’ve submitted the form and make sure you use “ATTN: WPMU DEV support – wp.org” as the email subject.`

    Kind Regards,
    Saurabh

    Plugin Author Hassan Akhtar

    (@khaxan)

    2 days, 12 hours ago

    @zimbo000 sometimes when the hosting has very aggressive caching, some code from the previous version can be included during the upgrade, which causes such issues. However in such cases the problem is usually temporary and it starts functioning correctly after the full upgrade.

    Thread Starter zimbo000

    (@zimbo000)

    2 days, 3 hours ago

    @wpmudev-support7

    Email sent. The issue has not re-occurred and went away after deactivating and reactivating the plugin.

    The difference this time (from the previous two ‘crashes’ as documented in this thread https://wordpress.org/support/topic/update-crashes-site-6/) was that the site itself did actually crash this time and I had to use the link WordPress provided in the “Your Site is Experiencing a Technical Issue” email to log back and deactivate the plugin. The normal WordPress login page would not allow me in.

    The previous two times when I did the update, I got the ‘critical error’ page displayed on the browser tab I was logged in on, but the site remained live on another browser tab. Before, when I killed the ‘critical error’ tab that I had been logged in on, I could simply re-load the WordPress login page and login as normal. Not sure if this is relevant.

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    8 hours, 15 minutes ago

    Hi @zimbo000,

    Thanks for sharing the site info. I have passed this to our team to check whether that helps rule out what might have occurred.

    However, as stated by @khaxan in the previous response such behaviour are temporary.

    Will keep you posted once we get further updates.

    Regards,

    Nithin

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.