About a month ago, I selected the latest version of Blazy on the admin/modules/update page and downloaded the update. Upon performing the update.php for the site I received and still receive the following error message: "The website encountered an unexpected error. Please try again later."

Running update.php for the site still results in the error "The website encountered an unexpected error. Please try again later."

How can I eliminate the problem without bricking my site? I am trying to upgrade to Drupal 9 from Drupal 8 and am currently running Drupal 8.9.20 with no other problems until I tried the update.php noted above.

Upgrade to drupal 9.

None

None

None

CommentFileSizeAuthor
Blazy Brick.jpg273.92 KBgeneatwell

Comments

geneatwell created an issue. See original summary.

gausarts’s picture

gausarts commented

Thank you. And I am truly sorry for inconviences.

May I know the exact error message?

Have you tried 2.9?

It has only 1 reported bug so far, related to PHP7.3, likely below PHP 8, specific to Layout builder page.

If that sounds your potential issue, please see the open issue for easy solutions before updating to 2.9.
Shortly, just disable Admin CSS at Blazy UI.

If worried, please lock your Blazy at 2.5 till we have less fatal bugs.

It had 2 bugs, none fatal, less chaotic.

Let me know.

geneatwell’s picture

geneatwell commented

Thanks for the quick response!
I uninstalled the package, did an update.php and it's somehow caused the following error:
"Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.
User
The User ID field needs to be updated."
While it allows me now to upgrade to drupal 9, the site does not allow me to log in with Drupal 9 so I have to revert to drupal 8 and try to fix this error.
Any ideas? It's a production site and entity updates cannot be accomplished with drush entity:update, drush entup or Devel Entity Updates.

gausarts’s picture

gausarts commented
Issue tags: -The website encountered an unexpected error. Please try again later.

> "Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.
User
The User ID field needs to be updated."
Hm, looks like unrelated to Blazy in this case, then. Even after Blazy was uninstalled?

You didn't mention about drush updb, might be related to that issue if not run.

> While it allows me now to upgrade to drupal 9, the site does not allow me to log in with Drupal 9 so I have to revert to drupal 8 and try to fix this error.
If still locked, consider drush uli. Not sure if that helps, though :)

If all failed, I would recommend testing any upgrades at staging or local till you resolved those issues, and sticking to D9 for a while and fix the errors on that branch. Reverting to D8 might cause such issues, and or other inconsistencies.

Let me know your findings.

geneatwell’s picture

geneatwell commented

The errors occurred only after Blazy was uninstalled and I accomplished the drush updb.

Accessing the site with drupal 8 is functional, but accessing the site with drupal 9 is not accessible. Reversion to drupal 8 is the only path forward.

Thanks for your help.

gausarts’s picture

gausarts commented

> The errors occurred only after Blazy was uninstalled...
By the current limited error message (The User ID field needs to be updated.), it didn't sound like Blazy is the culprit.
If Blazy, there had to be some more relevant info related to it.

"The User ID" is not anything that Blazy touched.
But I understand potential complication due to various upgrade issues, reversion, etc. when you uninstalled it which made Blazy was the closest culprit.

Could you check potential errors related to Blazy from any below:

  • The watchdog (/admin/reports/dblog).
  • Or perhaps from the end of your error_log file contents.
    At nginx, they can be anywhere as you defined. At some hostings they are normally at your document root or above.

Or better fix that particular error first, try the forum, you might not be alone with that issues :)

gausarts’s picture

gausarts commented
Component: Miscellaneous » Regression
Status: Active » Fixed
Parent issue: » #3257511: Optimization pre Blazy 3

Should be "cannot reproduce" based on #6, but let's stick it for 2 weeks to avoid dups.

A friendly housekeeping for a new hot fix release.

RC1 was just landed with a few regression fixes:
https://www.drupal.org/project/blazy/releases/8.x-2.10-rc1

A huge dev turbulence had subsided, we are almost back in business :)

Do not hesitate to re-open if any related info to work out as requested at comment #6.

gausarts’s picture

gausarts commented
Parent issue: #3257511: Optimization pre Blazy 3 »
Related issues: +#3257511: Optimization pre Blazy 3

Side effects should be related, not a child issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.