10.8.0 Update Error

  • captaincrank

    (@captaincrank)


    21 hours, 19 minutes ago

    Website is functional, but received the following WP error email:

    Error Details
    =============
    An error of type E_ERROR was caused in line 237 of the file /home/customer/www/domain.com/public_html/wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php. Error message: Uncaught Error: Class 'Automattic\WooCommerce\Enums\DefaultCustomerAddress' not found in /home/customer/www/domain.com/public_html/wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php:237
    Stack trace:
    #0 /home/customer/www/domain.com/public_html/wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-page.php(412): WC_Settings_General->get_settings_for_default_section()
    #1 /home/customer/www/domain.com/public_html/wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-page.php(385): WC_Settings_Page->get_settings_for_section('')
    #2 /home/customer/www/domain.com/public_html/wp-content/plugins/woocommerce/includes/class-wc-register-wp-admin-settings.php(126): WC_Settings_Page->get_settings('')
    #3 /home/customer/www/domain.com/public_html/wp-includes/class-wp-hook.php(341): WC_Register_WP_Admin_Settings->register_page_settings(Array)
    #4 /home/customer/www/domain.com/public_html/wp-includes/plugin.ph
Viewing 15 replies - 1 through 15 (of 21 total)
1 2
  • ronbi13

    (@ronbi13)

    20 hours, 55 minutes ago

    I have a similar error

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    20 hours, 7 minutes ago

    Hi @captaincrank,

    Thank you for sharing the error details. This looks like the WooCommerce update may not have completed fully, which can sometimes leave some plugin files missing or out of sync after updating to version 10.8.0.

    Since the site is still functional, please try the following first:

    1. Go to Plugins, Installed Plugins and deactivate WooCommerce.
    2. Delete WooCommerce from the Plugins page. Your store data will not be removed.
    3. Download a fresh copy of WooCommerce and reinstall it:
      https://ww.wp.xz.cn/plugins/woocommerce/
    4. Reactivate WooCommerce and check if the error persists.

    If the issue continues afterward, please share your System Status Report via https://pastebin.com or https://quickforget.com so we can take a closer look.

    You can get it from WooCommerce, Status, System Status, then “Copy for support”.

    Also, if you have any server or fatal error logs around the time of the update, please share those as well.

    ll09

    (@ll09)

    19 hours, 35 minutes ago

    I received the same error while updating 2 different Woo sites. I don’t think reinstalling is going to fix it. But nothing visible appears broken in the frontend.

    I’ll leave OP to send the pastebin since it’s their thread.

    gsibert

    (@gsibert)

    18 hours, 36 minutes ago

    Same for me, but can’t access any products post fail, so definitely visible errors.

    fox-didl

    (@fox-didl)

    18 hours, 32 minutes ago

    Same error on staging site:

    Ein Fehler vom Typ E_ERROR wurde in der Zeile 237 der Datei /wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php verursacht. Fehlermeldung: Uncaught Error: Class “Automattic\WooCommerce\Enums\DefaultCustomerAddress” not found in /wp-content/plugins/woocommerce/includes/admin/settings/class-wc-settings-general.php:237

    Thread Starter captaincrank

    (@captaincrank)

    17 hours, 20 minutes ago

    What I did was restore the prior version of WC from my server then updated to 10.8.0 again and had no errors. All appears to be working well at the moment.

    vaka2vaka

    (@vaka2vaka)

    16 hours, 43 minutes ago

    Error on site 11 out of 12. Visually, there are no problems.

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    11 hours, 18 minutes ago

    Hi @captaincrank, @ronbi13, @ll09, @gsibert, @fox-didl, and @vaka2vaka,

    Thank you all for sharing your experiences here and for confirming that this appears to have affected multiple sites after updating to WooCommerce 10.8.0.

    Also, thank you @captaincrank for sharing the workaround that helped on your end. It is appreciated.

    For anyone else running into the same issue, restoring the previous WooCommerce version first, then updating again to 10.8.0, appears to have resolved the problem successfully in this case.

    You can also try a fresh reinstall of WooCommerce by downloading a new copy here: https://ww.wp.xz.cn/plugins/woocommerce/. This process does not remove your store data.

    Before making changes, we strongly recommend creating a full backup and, if possible, testing first on a staging site.

    If anyone continues to experience the issue after reinstalling or updating again, please share your System Status Report via https://pastebin.com or https://quickforget.com so we can investigate further.

    momo-fr

    (@momo-fr)

    10 hours, 38 minutes ago

    I have a similar error

    vasilisweb

    (@vasilisweb)

    10 hours, 38 minutes ago

    So, just to confirm, it should be safe to update to version 10.8.0, correct?

    However, if the issue occurs again and the update fails, would it be enough to simply roll back and run the update again, or would I need to completely reinstall WooCommerce?

    But reinstall in which way?

    • By deleting and installing the plugin but i guess that i will not lose the data correct?
    • By overriding the plugin on upload plugin?
    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    10 hours, 20 minutes ago

    Hi @momo-fr and @vasilisweb,

    Thank you both for chiming in and sharing your experience with this update issue.

    At the moment, this appears to be related to some WooCommerce 10.8.0 updates not completing fully on certain sites, which can leave some files missing or out of sync temporarily during the update process.

    Based on the reports shared here so far, including @captaincrank’s workaround, it does appear safe to update to 10.8.0. In cases where the error occurred, rolling back to the previous WooCommerce version and then running the update again has successfully resolved the issue for several users.

    In many cases, simply reinstalling or updating WooCommerce again is enough and a full reinstall is not always necessary. You can download a fresh copy here if needed: https://ww.wp.xz.cn/plugins/woocommerce/

    Before updating, please make sure you have a full backup available and, if possible, test first on a staging site.

    momo-fr

    (@momo-fr)

    10 hours, 17 minutes ago

    Hi, I am updating by overwriting an upload of the latest version, this seems to resolve the issue, I can disable recovery mode without any problems.

    gerold1968

    (@gerold1968)

    10 hours, 8 minutes ago

    Same here… oh, you WOO Ninjas, this is the second time an update of the plugin gives us these errors. And as it seems for a lot of people out there its the same. Shit happens, but what about testing your updates a little better before releasing?

    vaka2vaka

    (@vaka2vaka)

    10 hours, 7 minutes ago

    If I install a previous version and then update the plugin again, I won’t receive a warning email, but it will show up as a fatal error in the status log. There are no visible issues with the sites.

    View log file – fatal-errors

    • This reply was modified 10 hours, 6 minutes ago by vaka2vaka.
    • This reply was modified 10 hours, 5 minutes ago by vaka2vaka.
    • This reply was modified 10 hours, 3 minutes ago by vaka2vaka.
    gerold1968

    (@gerold1968)

    9 hours, 41 minutes ago

    Manual download of the plugin file and re-installing it did the trick in my case.

Viewing 15 replies - 1 through 15 (of 21 total)
1 2

You must be logged in to reply to this topic.