Same error for me on several sites
Hi everyone,
Thank you all for your continued reports and for sharing what’s working. It’s genuinely helpful.
@gerold1968 Happy to hear that manually reinstalling did the trick.
@youlikeitmobilus we’re sorry to hear that. Could you do the same and let us know?
For your information: out of the 7 stores that were updated (production and development), 5 experienced the update problem and 2 did not (1 in production and 1 in development).
I ignored the error at the time, but then I compared the plugin files from my website with the zip file of the plugin that I downloaded from your website. They are completely identical. I used the MELD utility in Linux to compare them. It compared the files line by line and found no differences. However, it is strange that this is happening. Do you have any ideas about why the error is occurring if the files are identical?
Why do I receive an error email if the plugin files are updated correctly?
Hi @ronbi13,
Great piece of investigation, and actually very reassuring! The fact that the files are completely identical confirms this wasn’t a file corruption or incomplete download issue.
What happened is a PHP OPcache/autoloader timing issue during the update process. When WordPress runs the update, there’s a brief window where the old cached version of the autoloader is still loaded in PHP’s memory while new files have already been written to disk. During that window, the DefaultCustomerAddress class exists on disk but isn’t yet available to PHP, causing the fatal error. Once the update completed and PHP’s cache refreshed, everything resolved itself. The devs are also investigating this. The related PR is here.
Since your site is working correctly and the files are identical to the official release, no further action is needed. The error in your log was transient and is now resolved.
@momo-fr to easily track your issue, could you please create a new topic? That way, we don’t get lost among other reports.
Am I imagining it or has the 10.8.0 version been pulled? I tried twice; updated, got the error, rolled back. Try again, same story, rolled back. Now on 10.7.0, and no further updates in sight. What’s going on?
I decided to update other sites to version 10.8.0 but I also see that it is missing from the repository. Why?
Now 10.8.1 is out….
Might give it a wait. I’m in the middle of launching a brand new store, on 10.7.0. Ain’t got time for all this rollin’ around.
-
This reply was modified 1 day, 6 hours ago by
Sean.
Hi @sean-h , @ronbi13
Thank you for your patience and cooperation.
I would like to inform you that this issue has been fixed in the latest version, WooCommerce 10.8.1. Could you please update WooCommerce to the latest version and check whether you are still experiencing the same issue?
Thank you! The updates of my other websites went from version 10.7.0 to version 10,8,1 without any problems.