- Issue created by @maxilein
- ππΊHungary GΓ‘bor Hojtsy Hungary
Is this included in the error like this?
No! This is not for you! Your Drupal installation does not support utf8mb4. Have a fruitless look at https://www.drupal.org/docs/7/api/schema-api/data-types/encoding-collati β ... and then forget this module."
- ππΊHungary GΓ‘bor Hojtsy Hungary
Googling for that specific error message it comes up from https://www.drupal.org/forum/support/module-development-and-code-questio... β , looks like you either use that custom module or someone very strongly got inspired by that code (copy-pasted it). This would be output when that code is run (since it echos and dies). The container in this case is not yet initiatialized because the error happens in a global context while the codebase is being assembled. Look at your own site codebase to find this code.
- π¦πΉAustria maxilein
Thank you very much.
I found it in the wayback filer module β .
I will move the issue there. - π¦πΉAustria maxilein
There seems to be an incomplete install routine (in \wayback_filter\wayback_filter.install) that causes errors when running upgrade_status.
Why do you need this routine?
Was it copied from somewhere and forgotten or does it fullfill a purpose? - π©π°Denmark Steven Snedker
I'm so sorry for
a) Not seeing this until now
b) Making such a shoddy error messageThe utf8mb4 check in the install file has now been vastly improved.
Is it still useful?
My guess is that 99% of people running Drupal 10, 11 do it on a database using utf8mb4.Yet, I made a utf8mb4 check in the install file in order to save the few poor souls not using utf8mb4 from a White Screen of Death upon installation.
Phpstan should not choke on version 1.2.1. My apologies for the old, shoddy version.
- Assigned to Steven Snedker
- Status changed to Fixed
3 months ago 5:00pm 17 December 2024 Automatically closed - issue fixed for 2 weeks with no activity.