I try to upgrade my thunder installation from 2.x to 3.x according to the manual: https://thunder.github.io/thunder-documentation/update-2-to-3
But I get stuck at step "Execute media update" with this error message when I want to run "drush cr":
The service "blazy.oembed" has a dependency on a non-existent service "media.oembed.resource_fetcher".
Somehow drupal/blazy needs to be 1.x to upgrade media module but if I follow the instrudctions drupal core gets upgraded and with it drupal/blazy. i tried to upgrade media beforehand but that does not work as thunder needs entity manager in version 1.8. Somehow it's a dep deadlock. How can I solve it?
composer require drupal/media_entity:^2.0 drupal/media_entity_image drupal/video_embed_field:^2.2
Using version ^1.3 for drupal/media_entity_image
./composer.json has been updated
Removing package drupal/entity_browser so that it can be re-installed and re-patched.
- Removing drupal/entity_browser (1.8.0)
Deleting docroot/modules/contrib/entity_browser - deleted
Removing package drupal/inline_entity_form so that it can be re-installed and re-patched.
- Removing drupal/inline_entity_form (1.0.0-rc2)
Deleting docroot/modules/contrib/inline_entity_form - deleted
Removing package drupal/redirect so that it can be re-installed and re-patched.
- Removing drupal/redirect (1.5.0)
Deleting docroot/modules/contrib/redirect - deleted
> DrupalProject\composer\ScriptHandler::checkComposerVersion
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- burdamagazinorg/thunder 8.2.52 requires drupal/media_entity 1.8 -> satisfiable by drupal/media_entity[1.8.0] but these conflict with your requirements or minimum-stability.
- burdamagazinorg/thunder 8.2.52 requires drupal/media_entity 1.8 -> satisfiable by drupal/media_entity[1.8.0] but these conflict with your requirements or minimum-stability.
- burdamagazinorg/thunder 8.2.52 requires drupal/media_entity 1.8 -> satisfiable by drupal/media_entity[1.8.0] but these conflict with your requirements or minimum-stability.
- Installation request for burdamagazinorg/thunder (locked at 8.2.52, required as ~8.2) -> satisfiable by burdamagazinorg/thunder[8.2.52].
Installation failed, reverting ./composer.json to its original content.
Comments
Comment #2
TiMESPLiNTER commentedComment #3
TiMESPLiNTER commentedComment #4
daniel.bosenHello, You have to make sure, that you do not do a
drush crbefore thedrush updb. That is very important.If you did, you will propably have to start at the beginning of the process with the Thunder 2 codebase.
Comment #5
TiMESPLiNTER commentedI didn't do a
drush crbeforedrush updb.drush updbworks fine but thedrush crafter the updb aborts with the error message mentioned above. I did follow the documentation step by step and ended up with this error.Comment #6
daniel.bosenAh ok, I just wanted to make sure! I see in the composer output,
burdamagazinorg/thunder 8.2.52 requires drupal/media_entity 1.8, This looks like The commandscomposer remove burdamagazinorg/thunderorcomposer require "thunder/thunder-distribution:~3.3" --no-updatemight have failed.If you like, you can also post your composer.json, then I could try out myself.
Comment #7
TiMESPLiNTER commentedSorry maybe my initial post is a bit confusing. The composer dep error message came from my second attempt to upgrade media first before migrating thunder to version 3 after my first attempt failed with official manual page I linked in my initial post. So the the two attempts are not related to each other.
But maybe I could uninstall thunder and then migrate to Media 2.0 and then do the rest of it according to the manual page?
Comment #8
TiMESPLiNTER commentedOkay, I solved it by chance. When I executed
drush updbit told me always that there are no updates. I then went to /update.php in my browser and there were many updates to apply so I executed them and after that everything was fine.Not sure why drush showed me no updates for my drupal installation though.
Comment #9
daniel.bosenThanks for posting back! That is really strange. But I am glad, that you finally got through the update!
Comment #11
it-cruFor our update from Thunder2 to Thunder3 hosted on Acquia Cloud environments following steps worked to solve this issue during deployments.
drush9 -l https://www.example.com updb --yes(replace www.example.com with your domain name)Comment #12
sergiu.popa commentedI'm getting the same message on the last step, after updating the database, when I want to rebuild the cache (before removing contrib media, last step). These are the exact steps I follow, after the guide:
When I update the database, I get an error but I confirm I continue:
It completes most of the operation, except finishing with these errors:
Then when trying to rebuild the cache, I can't:
I attached the composer.json start and end files, and the output from steps 3 and 5.
What am I missing here? Any help is appreciated. Thank you!