Filter module page on project name

Yeah, I can see how that'd be useful.

I'm not sure that path is going to work, though, since we already have admin/config/modules/[action], where [action] can be any of uninstall, install, and update. So, we're going to have namespace collisions this way, if any projects are named that. I think we're going to need another layer in the path, something like:

admin/config/modules/by-project/[project_name]

Although I bet someone's going to have a hissy fit about having "project" appear in the UI like that. *shrug*

But yeah, this could be cool, and a potentially nice UX cleanup once #538660: Move update manager upgrade process into new authorize.php file (and make it actually work) and 10/15 is behind us...

Tagging for UX folks...

Derek asked me whether or not this falls under UX clean-up. IMO this is just a different view of a page we already have, so is not the kind of thing that's going to cause a big fall-out mess to clean up (unlike #607008: Fix bugs in https support and force using https for authorize.php if available), so I'm fine with this coming up under UX clean-up.

So, I am somewhat disturbed by the possible fall-out from this patch. Can't we just redirect to the certain part of the admin/config page? I am asking this, because we want to avoid confusing people straight off - as to where a certain module lives in our categorisation.

So A filterd module page on project name?

Jacob: The latter in 3.5 weeks no way, the former - Sure. Lets do it.

Thanks for the patch. I'm still struggling with applying patches, could somebody provide some screenshots?

Here two snapshots.

BTW Please notice that I have added manually a line to all devel info files(Since I was using devel 8.x branch). The only visible project is devel, because project key is not included on core dev branch module info files(only by the packager).

Thanks for that. I'm not sure though I understand what's happening here. There's a new tab 'List by project' with links to what? Newly installed contrib or all contrib? Then click a link there to show all modules that belong to that module package?

How do you get to this 'list by project' tab: do you have to click it yourself or is there a link in the 'succes, x modules enabled' message after enabling new modules?

These seem related:
#89205: Usability: Better message on module activation/deativation
#396478: Searchable modules page

Hey, I forgot completely to provide a good message that explains what I have tried, so let's try to do it here.

• Add a 'project' parameter to the system_modules form callback, which does the filter based on the module info project key.
• Add two menu entries.
  • One for 'List by Project' tab, which lists(and links to the other menu entry) all the projects known(again based on module info project key).
  • The other, which based on the last parameter pass it to the modified system_module form callback.

So, now let's try to answer the questions:

There's a new tab 'List by project' with links to what? Newly installed contrib or all contrib? Then click a link there to show all modules that belong to that module package?

It uses the parsed information, and iterates through all projects known(it doesn't matter if they are core or contrib, but only showing devel in the list because project key on info files are added only with release tarballs, and locally I was using current 8.x branch), showing them with a link to the new menu entry with the needed filter(the project name).

How do you get to this 'list by project' tab: do you have to click it yourself or is there a link in the 'succes, x modules enabled' message after enabling new modules?

There is no currently a link on that message, but adding it will be trivial ;-), and maybe it can be part of #89205: Usability: Better message on module activation/deativation.

I have taken a look to #396478: Searchable modules page, and that issue kind-of trying to solve the similar problem(actually this is a subset), but with a different approach, they use javascript to make the filter(and search within all table data), I use a menu callback and search only by the module info project key.

error: patch failed: core/modules/system/system.admin.inc:761
error: core/modules/system/system.admin.inc: patch does not apply
error: patch failed: core/modules/system/system.module:2445
error: core/modules/system/system.module: patch does not apply

patch no longer applies.

https://drupal.org/project/module_filter seems like a better implementation of this idea imo.

#396478: Searchable modules page introduced a filter on the modules page. I think this can be closed as a duplicate of that one.