Sure, experienced devs and people that have drush/bee available would run drush pml or bee pml and grab a lists of modules, but this person on the forum posted multiple screenshots of the modules listing page when asked: https://forum.backdropcms.org/comment/3572#comment-3572 ...and they had to do it in multiple screenshots, in multiple posts.
When later they mentioned that they had the same issue on a different site, and asked to compare the versions of modules between the 2 sites, they responded:
a lot are common difficult to say it can take hours to test
If Backdrop core allowed the person to easily extract plain-text lists of the modules on each site, then it would be easier for them to compare the lists.
I would like us to introduce an easy way (under the rest of the site reports I guess), to allow people to get a plain-text list of modules/themes/layouts etc., which they can then copy/paste to forum posts and issues if that is requested of them.
Another thought is to add "export" links/buttons in key pages, like the site status report, that would allow people to grab a plain-text list of php, version, db type/version, web server type/version etc.
All that would allow us to provide instructions like the bellow in issue templates (fictional scenario - assumptions about the way we implement this feature):
- Navigate to Reports -> Status report using the admin bar at the top of the site
- Click the "Copy basic information" link at the top-right of the page.
- Paste this information here.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists