Open jenlampton opened 5 months ago
To clarify: the bee command would help those using the command line, whereas the plain-text list would allow to use the manual installation feature of the project installer (paste the list of module machine names in the text box and click "Install"):
@klonos , this is great suggestion. What is correct names for modules, like "rules-1.x-2.x.zip" or something else?
What is correct names for modules
It's the lower-case machine name of the module.
@jenlampton , it would be great to have this in help text instead of "Names must only contain lowercase letters, numbers, and underscores." I can probably submit PR for this change in core, but maybe it is easier if you make this change directly? Let me know what is easier for you :) thanks for clarification!
I can probably submit PR for this change in core, but maybe it is easier if you make this change directly?
We can't make any changes to backdrop core directly, everything needs to come through via PR.
I will add PR for help text, I would like to combine it with this list of modules that can be pasted into manual install window.
this list of modules that can be pasted into manual install window.
While I'm working on this, here's a drush command that will get you the same thing
drush pm:list --type module --status=enabled
Marked RTBC on Drupal.org https://www.drupal.org/project/backdrop_upgrade_status/issues/3440522#comment-15554944
Sorry @irinaz, I thought I had provided feedback on this issue previously -- but I don't see a comment either here or in the d.o issue.
I didn't want to merge that change as-is because I don't think the information belongs on the "Report" / "Overview" 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 should go on the status report page, maybe?
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 you had the complete list of modules, so maybe that's all we need to add.
The complete list of modules should go on the status report page, maybe?
Or, we could add two items: 1) the complete list of modules on the D7 site and 2) the complete list of Backdrop modules. This would better highlight the differences between the two. This could be especially helpful for module name changes, and for when contrib things move into core.
The logic for putting this list on the backdrop status report is the flow for someone who is migrating to backdrop.
If you are preparing your backdrop codebase while looking at the BUS module report, it would be helpful to have a list of all modules needed for Backdrop (including the names of the recommended replacements) for setting up your Backdop site.
(Request from @irinaz )