Problem/Motivation
We need to manually test that the upgrade path from Quick Edit in core in 9.5.x to contrib in 10.0.x is smooth.
Steps to reproduce
Proposed resolution
Use @bbrala's excellent instructions for Color module as a basis: #3302799: Manually test color module removal
Install Drupal 9.4
- Install Drupal 9.4
composer create-project drupal/recommended-project:9.4.* drupal-quickedit - Move into the directory
cd drupal-quickedit - Enable development settings
cp web/sites/example.settings.local.php web/sites/default/settings.local.php - Add Drush
composer require drush/drush - Install with Umami
vendor/bin/drush si demo_umami - Enable settings.local.php at the end of
web/sites/default/settings.php
Enable and test Quick Edit
- Enable the module
vendor/bin/drush en -y quickedit - Log into the site and use Quick Edit to make some changes.
Choose your own adventure
At this point, you can either test what happens if you install the contrib Quick Edit or not.
Either upgrade to contrib and test again
-
composer require drupal/quickedit vendor/bin/drush cr - Log into the site and use Quick Edit to make some changes.
Or do nothing and expect errors at the next phase
If you don't install the contrib project, and do not uninstall the core version before you upgrade, you should get errors via update.php (and warnings via drush updb) about the missing core module. See also #3294914: Create dedicated error section for missing removed core modules/themes on update.
Upgrade to Drupal 10 and test again
-
composer config minimum-stability dev composer require drupal/core-composer-scaffold:10.0.x-dev drupal/core-project-message:10.0.x-dev drupal/core-recommended:10.0.x-dev drush/drush -W - Remove the core copy of Quick Edit. Either:
- Apply latest patch from #3227033: Remove Quick Edit from core
rm -rf web/core/modules/quickedit
- Update to D10. Either:
- Via the UI: visit
update.phpfor the local test site - Via drush:
vendor/bin/drush updb vendor/bin/drush cr
- Via the UI: visit
- Log into the site and either:
- use Quick Edit to make some changes
- or experience errors at
admin/reports/status
Comments
Comment #2
longwaveD10 compatibility requires the patch from #3291700: new subtree split of core Quick Edit into contrib (v2).
Install Drupal 9.4
composer create-project drupal/recommended-project:9.4.* drupal-quickeditcd drupal-quickeditcp web/sites/example.settings.local.php web/sites/settings.local.phpcomposer require drush/drushvendor/bin/drush si demo_umamiEnable and test Quick Edit
vendor/bin/drush en -y quickeditUpgrade to contrib and test again
Upgrade to patched Quick Edit
Upgrade to Drupal 10 and test again
Comment #3
dwwQE 1.0.2 is now out. 🎉
Moving the instructions into the summary, and simplifying them since you no longer need to patch anything.
Comment #4
dwwI've tried this now myself, so I'd call it RTBC, but that'd sort of be like doing so on my own patch. 😅
Comment #5
dwwPer @catch, adding an explicit step to remove D10 core quickedit.
Comment #6
longwaveI think it is fine for anyone to RTBC this if they followed my steps and got the same result, whether they are maintainer of the module or not :)
Comment #7
dwwSure, but I didn’t follow your steps. I changed the steps considerably, so they’re now “our” steps and I don’t think my hands are clean enough to RTBC now. 😅
Comment #8
dwwAdded notes about testing what happens if you enable core 9.4.* QE, do not install contrib, and try to upgrade to D10.
Comment #9
dwwComment #10
catchHate to ask this, but was 10.x tested without lines like this in core: https://git.drupalcode.org/project/drupal/-/merge_requests/2389#note_112760
Comment #11
longwaveThe Quick Edit metadata issue will be resolved in contrib by #3304893: Add Quick Edit metadata to core field formatters when @dww returns and also committed to 9.5.x in #3270434: Mark Quick Edit deprecated.
Comment #12
bbralaI've went through the whole process outlines by longwave. Quick edit basically works as intented. I used the path of installing quickedit in 9, then upgrading. The path is smooth as stone. No logged errors, no js errors, quickedit works.
The comment by catch in #10 as that been been extensively tested by @catch in the related issue.
This is great! RTBC <3 :)
Comment #13
xjmHooray!