- Issue created by @fkelly
- 🇺🇸United States fkelly
Seeing the announcement for Drupal 11.1.3 at
https://www.drupal.org/project/drupal/releases/11.1.3 →
(and recognizing that it was a security related issue) I went to follow the steps for the update. Retrospectively I should probably have realized that "Sites on Drupal 10.4.x should update immediately to Drupal 10.4.3" in the announcement meant exactly what it said and that I was stepping into quicksand by trying to go straight to 11.1.3. What I didn't realize was that
https://www.drupal.org/docs/upgrading-drupal/upgrading-from-drupal-8-or-... →
existed and that this update was not like other updates I have been doing for the last several years and that I couldn't "cut corners". But I didn't. The update from 10.4 to 11 had to be done very differently from the previous updates.
It was only when the composer update process went completely wrong and I did some searching that I found that at least one other user had fallen into a similar "trap" I had and that Ressa had directed him to the upgrading from drupal 10-to-drupal 11 document.
To save others from this pain cave, perhaps in:
https://www.drupal.org/project/drupal/releases/11.1.3 →
you could add a big bold warning that if you are coming from Drupal 10 you should consult that document and not simply type:
"composer require drupal/core-recommended:11.1.3 drupal/core-composer-scaffold:11.1.3 drupal/core-project-message:11.1.3 --update-with-all-dependencies" or other equivalent composer commands that presuppose you are at Drupal 11 already.
- 🇬🇧United Kingdom catch
We explicitly don't want people to update from 10.4 to 11.1 just to get the security release, they should update to https://www.drupal.org/project/drupal/releases/10.4.3 → . So including instructions on how to update from Drupal 10 to 11 would probably result in more people running into the problems you had.
Would it have helped if 10.4.3 was listed more prominently (and linked) in the release notes?
- 🇺🇸United States fkelly
@catch ... anything in the release notes that would have warned people off from trying to update to 11.x just to get the security fixes would have helped. The documentation for
https://www.drupal.org/docs/upgrading-drupal/upgrading-from-drupal-8-or-... →
was very helpful but not if a user was not aware that it existed. I had other reasons for wanting to get my site to Drupal 11 "prematurely". I help maintain a contrib module (Juicebox) and wanted to be able to tell the users that it worked with Drupal 11. I will mark this as closed.
Additionally there is a specific release announcement for 10.4.3 → .