By rfmp on
Hello,
I'm just trying to upgrade from D9, latest version, to D10, latest version. I followed the steps in this document and succeeded until #4.4, which means that D10 is installed and 'composer install' is executed, everything successfully without any errors. But now, when I visit my site, I get an HTTP error 500, internal server error. That means also that I cannot run database updates.
I should mention that all modules were installed with the GUI, not with composer. (Of course I removed deprecated modules before I began to upgrade my site.) So, there are no dependencies in my composer.json.
What can I do now?
Reiner
Comments
all modules were installed
This means that there are no compatibility checks being performed for your modules - I would guess that your problem will likely like here - an incompatible module with the current version of Drupal. That and/or one of the modules installed through the GUI needing an underlying library upgrade, which Composer handles automatically when modules are added/updated.
However, you can try running
drush updbanddrush cr, to see if this fixes it. If you're lucky it will! If not, then the next thing to do is figure out what the specific error you are facing is. You will need to enable verbose error reporting, and reload the page. This will show you the error and stack trace, which then tells you where to start looking.Contact me to contract me for D7 -> D10/11 migrations.
An HTTP 500 error after the
An HTTP 500 error after the Composer phase usually means there is a PHP fatal error happening under the hood that the browser isn't showing you .since you mentioned your modules were installed via the GUI and not Composer
When you upgrade the Drupal core to 10, many underlying Symfony components change. Modules installed through the GUI don't get their dependencies updated by Composer, so they are likely trying to call code that no longer exists in the new core.
Check the Server Log :Look at your PHP error logs or the watchdog table (if you can access it via Drush). It will tell you exactly which module is throwing the 'Fatal Error.The Drush Rescue: If you have terminal access, try running
drush cranddrush updb. Often, the error message in the terminal is much more descriptive than the 500 page.Manual Compatibility Check: Since Composer isn't managing your modules, you’ll need to manually verify that every module in/modulesis actually Drupal 10 compatible. If one isn't, try moving it out of the folder temporarily to see if the site loads.Switch to Composer: Long term, I’d really recommend 'Composerizing' those modules. It’s a bit of a headache upfront, but it prevents exactly this kind of version mismatch.Hope this helps you get back online
Thank you guys for your help
Thank you guys for your help and hints! I'm just doing everything once again and have a closer look at everything. I discovered two modules that have a D9 release and a D10 | 11 release but no release for D9 | 10. (forum access and ACL) So I have to replace them. My second task of upgrading ist still in progress, I'll come back to you later.
Nice catch! Glad you found
Nice catch! Glad you found those D9 modules causing the issue. Good luck with the rest of the upgrade—let us know if you run into anything else
It works!
OK, my D10 site finally runs. :-) The main thing was that I had to delete a couple of modules that were not D10 compatible. Among them such essential ones as token and metatag, which I used extensively. Then I could upgrade. Afterwards I still got an error when visiting my site but it was a different one. I altered settings.php in order to be able to run updates. I could visit my site then /uodate.php and saw that 1 had a wrong PHP version, which I fixed immediately. Then I could run update.php, something like 80 updates where made without errors. Now my D10 dev site ist running. Of course, there ist still much to do but that's OK. There is no critical task anymore.
Again thanks for your contributions!
Reiner
Glad you got it worked out.
Glad you got it worked out.
If I were in your position, the next thing I would do is figure out how to get all my modules managed by composer, so that compatibility checks are performed in the future. Good luck!
Contact me to contract me for D7 -> D10/11 migrations.