Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.It would be really useful if there was a clear way to download additional information about a project, e.g. where it's from, if it's part of core, contrib or custom, what type of project it is, what the current version is/are, etc. Then, on the project view page, it should show a summary of this information along with a list of the sites that use it and what version they're using, maybe with a green bar indicating it's up to date, a yellow bar for out of date and a red bar for out of date with a security update available.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | project ctools.png | 140.58 KB | jurgenhaas |
| #3 | projects overview.jpg | 99.51 KB | jurgenhaas |
Comments
Comment #2
DamienMcKennaI guess a relevant question here would be whether this is something you'd like in the main platform or if it would be something that would be done as a custom improvement?
Comment #3
jurgenhaasThe answer is certainly yes, and probably most of it is already available and probably just needs some tweaking. Let me give you an example. When I have collected all project usage from all my remote sites and also collected project status information from drupal.org, then I get two thing: a project overview page and a project detail page. How to setup e.g. cron jobs to regularly update those details can be found in the documentation.
The projects overview gives you one line per project and core version together with an indicator of the update status (except for Drupal 6 of course):
When you then click on one of the projects, you get a list of installed versions for that project and for each of those versions a list of domains where this is installed:
That sounds like 80% of what you've asked for, when I got you right.
What's missing are some project metadata like this:
All these are already available in the drd_project, drd_major and drd_release database tables and we only need to render them. Some of this (e.g. the download and release links) are already there on the project details page for those release that have available updates. In the screenshot that's the case for ctools version 7.x-1.11. Also, when you go to a core or domain detail page, you get a list of projects there too and that list also contains all of those links.
Other details shouldn't be difficult to add to the projects detail page.
Now, one last note about what projects we're displaying. Although we have all the projects for each domain in the database, it turned out that it's better to hide certain projects: those that are a sub-project of another project and those that have a hidden flag which is the case for e.g. custom modules normally. Because of that, all modules from core are not displayed because you would never update them individually anyways, only as part of a core update.
Not sure if that assumption makes sense. If not, we could add a filter to the views which hides them by default but allows to enable them manually. Then we would have to think about what to display in the details, because the update status and links like with projects generally wouldn't make sense then, does it?
So, that's a long response. Probably we should have written more documentation a while ago ;-)
What do you think?
Comment #4
jurgenhaashttps://gitlab.com/drupalspoons/drd/-/issues/2