The entire site crashed after upgrade to D10.2.1

What was the update error?

When you are faced with a 500 error like this you have to check the logs. You must do that.

We don’t actually know there is a bug as yet so I am making this a support request until more information is available.

If you encounter one error it's best to figure out the cause of that and fix it first (in your case the issue you had with commerce) before upgrading anything else.

When you say you used the terminal what exactly did you do? Did you use update.php or drush updb to run the update scripts?

Clicking on any page, there is the error message on site is "The website encountered an unexpected error. Try again later." Unable to access any page.

I copied the code "% composer update "drupal/core-*" --with-all-dependencies" in terminal. No error message in terminal. I use terminal to upgrade core and install new modules.

I don't know what caused this problem. Longwave is right that I should resolve the commerce error before upgrading to D10.2.1, and backup before any updates. Lesson learned. A few observations:

• Commerce crash is for sure, because I had another D10.2 test site and update Commerce from that site, the same problem -- unable to update database.However, when I rebuild a new site, then install the newest commerce, no problem.
• With D10.2, I was able to install newest rule module (alpha), but with D10.2.1, the rule installation failed.

The most painful thing is I am unable to get those structure design over. I have one option field with a few hundreds of options. Since D10.2 no longer provides text area input that I can copy to, entering options one by one is very annoying and time consuming. Hope you can add that feature back in.

Let’s keep this support issue on-topic, which is regarding the current crashing. Consult the logs and provide the error details to obtain support.

You've done the composer update step of https://www.drupal.org/docs/updating-drupal/updating-drupal-core-via-com... → but you have not mentioned the database update step. This is required and may solve the error that you see on screen.

They actually did mention updating the database. Possibly some important updates were skipped because of whatever error that occurred.

The errors started when updating commerce -- in the process of updating database. The entire sites were not down at that time. But after updating core in terminal, the entire sites were down.

What worths repeated is that I tested updating commerce at another test site at D2.0, the SAME errors appear when updating database. So it seems commerce update in D2.0 has problems. Further I used terminal to update core, that sites were not entirely down then but when I went back to check it today, it is all down, too.

Unfortunately we will have to close this if we can't be shown the exception log.

Just restoring issue template and formatting for readability.

I went to database and exported the latest "recent log message". It shows:

a:6:{s:5:"%type";s:5:"Error";s:8:"@message";s:84:"Undefined constant CommerceGuys\Addressing\AddressFormat\AddressField::ADDRESS_LINE3";s:9:"%function";s:58:"Drupal\commerce_store\Entity\Store::baseFieldDefinitions()";s:5:"%file";s:84:"/Users/myusername/drupal/modules/contrib/commerce/modules/store/src/Entity/Store.php";s:5:"%line";i:374;s:17:"@backtrace_string";s:9488:"#0 /Users/myusername/drupal/core/lib/Drupal/Core/Entity/EntityFieldManager.php(230): Drupal\commerce_store\Entity\Store::baseFieldDefinitions(Object(Drupal\Core\Entity\ContentEntityType))

This looks like perhaps a version mismatch with commerce and the address module, or perhaps some patch is applied on that site.

Knowing precisely what you updated would go a long way to getting an answer.

Possible duplicate of 💬 website encountered error line 374 of Store.php ADDRESS_LINE3 Fixed

Seems you need to upgrade commerceguys/addressing to at least 2.0.

This issue, in the end, looks identical to that bug.

I do have the latest address module installed. All modules are up to date. I understand this issue doesn't have obvious clues to trace because the site is inaccessible at all.

I'm willing to let it go and start a new site.

Thank you all very much for trying to help and resolve this issue!

This issue has very obvious clues to trace. I don’t agree with your position on that.

It looks like you're running an outdated version of the commerceguys/addressing library which doesn't have the constant the Store entity is accessing. Are you sure your addressing library is up to date?