- Issue created by @irinaz
- 🇺🇸United States keiserjb
I have an implementation that adds a bee command that can be used on a new site install as well as a list that can be cut and pasted into the project installer.
- Merge request !3Adds lists of modules for command line and project installer. → (Open) created by keiserjb
- Status changed to RTBC
7 months ago 5:51pm 16 April 2024 - 🇺🇸United States irinaz
I tested this MR and it works as expected - provides list of modules that are not in BackdropCMS core and are enabled on D7 site. Marking RTBC
- Status changed to Needs work
7 months ago 4:20am 28 April 2024 - 🇺🇸United States jenlampton
I don't think this information belongs on the "Backdrop Upgrade Status Report" page. It doesn't have anything to do with how ready your site is for Backdrop (and the report page is already very long).
The complete list of modules could go on the Drupal Status Report page, maybe? We could add it there.
We could also add it to the top or bottom of the "Backdrop Upgrade status" page. That page already lists all the contrib modules so it seems like maybe a good fit.
I was also thinking that we could add a page for "Backdrop Upgrade Tools" (or something). A drush or bee command could go there. But neither would really be necessary if we had the complete list of modules, so maybe that's all we need to add.
- 🇺🇸United States jenlampton
I'm removing the installer module screenshot from the issue description since installer module in Backdrop, and Backdrop upgrades from Drupal 7 have nothing to do with each other. I know some people like to do upgrades that way but since that isn't supported (and can be dangerous) I don't want to encourage it ;)
We do still need the complete list of module machine names for supported upgrade paths (and people can use that list for whatever they want!)
Please also see the GitHub issue for more discussion and other possible solutions:
https://github.com/backdrop-contrib/backdrop_upgrade_status/issues/44