Hello,

I'm trying to upgrade from Thunder 8.x-2.47 to Thunder 8.x-3.0-rc1. I've tried several scenarios and reinstalls of my development database as I am trying to move to production with Thunder. I am told by Composer that I had to have the latest version of Thunder 2 before moving to Thunder 3. I now have the latest version of Thunder 2 (2.47) but still cannot upgrade to recommended Thunder 3.

I had to create my project using composer create-project burdamagazinorg/thunder-project because that one had the latest available Thunder 2 but no 3+ version while composer create-project thunder/thunder-project only had Thunder 3+ but no 2+ version.

Can someone provide the proper process to update Thunder without breaking my site and go from Thunder 2+ to Thunder 3+ with Composer?

There are several modules attached to Thunder 2+ that have major security holes such as Simple XML sitemap and Media Pinterest, as well as Paragraphs module being the old version. I cannot update these modules because Thunder will not allow this according to composer but I also cannot upgrade to Thunder 3.0+ because there are no updates available according to Composer. I've tried several dry runs including "composer update thunder/thunder-project thunder" and "composer update burdamagazinorg/thunder".

I often get conflicts like the following when try to plug these security holes from modules.

[mysitepathincommandline]composer require drupal/simple_sitemap:^3.3
./composer.json has been updated
> 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
    - Installation request for drupal/simple_sitemap ^3.3 -> satisfiable by drupal/simple_sitemap[3.x-dev, 3.3.0].
    - burdamagazinorg/thunder 8.2.47 requires drupal/simple_sitemap ^2.0 -> satisfiable by drupal/simple_sitemap[2.x-dev].
    - burdamagazinorg/thunder 8.2.47 requires drupal/simple_sitemap ^2.0 -> satisfiable by drupal/simple_sitemap[2.x-dev].
    - burdamagazinorg/thunder 8.2.47 requires drupal/simple_sitemap ^2.0 -> satisfiable by drupal/simple_sitemap[2.x-dev].
    - Conclusion: don't install drupal/simple_sitemap 2.x-dev
    - Installation request for burdamagazinorg/thunder (locked at 8.2.47, required as ^8.2) -> satisfiable by burdamagazinorg/thunder[8.2.47].

Again, can someone provide the proper process to update Thunder without breaking my site and go from Thunder 2+ to Thunder 3+ with Composer?

Thanks in advance

Comments

Dru Pal created an issue. See original summary.

daniel.bosen’s picture

Hello!

I will try and guide you through the process. Sorry for the inconvenience, but we had to make sure, that several things are updated to at least minimum version, and that is why we require everyone who is on a Thunder 2 version before 2.47 to upgrade to 2.47 first, before beeing able to upgrade to Thunder 3.

But first I have a few questions that need to be clarified, to really understand your situation and can give some advises:

I had to create my project using composer create-project burdamagazinorg/thunder-project because that one had the latest available Thunder 2 but no 3+ version while composer create-project thunder/thunder-project only had Thunder 3+ but no 2+ version.

Why did you have to create the burdamagazinorg/thunder-project? I was under the impression, that you already had a Thunder 2 project running?

dru pal’s picture

Hello daniel.bosen,

Why did you have to create the burdamagazinorg/thunder-project? I was under the impression, that you already had a Thunder 2 project running?

Yes, I have the latest Thunder 2 ( Thunder 8.x-2.47 ) running now, but I could only install it through the command composer create-project burdamagazinorg/thunder-project . The other command composer create-project thunder/thunder-project doesnt allow any install below Thunder 3, I even just tried to create a new project again to confirm it.

Here are my results

[mysitepath]# composer update --dry-run
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
    - The requested package thunder/thunder-distribution ^2.4 exists as thunder/thunder-distribution[3.3.0-beta1, 3.3.0-beta2, 3.3.0-beta3, 3.3.0-rc1, dev-8.x-2.x, dev-8.x-3.x, dev-feature/2828088-automatic-saving-of-content, dev-feature/2899254-integrate_editorial_search_with_search_api, dev-feature/2918993-add-translation-test, dev-feature/2933086-fb-instant-articles, dev-feature/3016921, dev-feature/3055350-remove-revision-log-from-inline-entity-form, dev-feature/3067847-media-library-switch, dev-feature/testsite-builder-media-field-widget-mapping, dev-fix/3054897-Linkit-icon-is-missing, dev-fix/3073791-paragraph-split-text-occasional-test-fail, dev-release/foo, dev-task/2977738-enable-jsonld-amp2, dev-task/3056095-update-js-libs, dev-task/3057530-update-simple-sitemap, dev-task/3058397-move-drush-make, dev-task/3065999-update-entity_browser, dev-task/update-documentation, dev-task/update-script, dev-update/paragraphs-1.9] but these are rejected by your constraint.
daniel.bosen’s picture

Are you on the drupal slack? I guess it would be easier to chat about this, instead of ping-ponging comments :-)
My username on the Drupal Slack is dbosen.

dru pal’s picture

I would want others to find the answer here too but I also messaged on slack

dru pal’s picture

I solved this but had to upgrade to the latest version 2.0 using composer create-project burdamagazinorg/thunder-project

Then transfer my database and create a new project under composer create-project thunder/thunder-project. Perhaps I could have edited the composer.json file but wasn't sure where all the other references were to the thunder project.

Not sure why it is set up this way, it would be nice if both version 2 and 3 and all versions were under composer create-project thunder/thunder-project

daniel.bosen’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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