Jump to:
| Project: | Enabled Modules |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Great module, very useful for deploying sites to a live server.
Some feature requests, I'm trying not to repeat those here.
http://drupal.org/node/244583
1. Display enabled modules in the same way that the admin/build/modules page is displayed, same groups etc.
Generally, people will know that they have uploaded core [optional and mandatory], but might be unsure which contrib modules need to be uploaded too.
2. Not sure how feasible this one is.
Rather than a separate page, could this be added as a tab to admin/build/modules, or even some fancy javascript which would highlight enabled modules or hide disabled modules on the admin/build/modules page.
In any case, thanks for a really useful module.
Alan
Comments
#1
Thanks Alan!
Agaric needed the basic functionality in the present module, and I spent far longer turning it into a module than we had time for. I'm very glad I did given the interest, but we don't have the time budget to put in every great feature request. And I'm part of the problem: personally I'm most interested in the "recently enabled" administrative aid promised in the module description, and that extends the module in still another direction.
We are happy to take patches; we could take sponsorship (and conversely would contribute financially to another developer or shop putting in the effort); or, if you think there's interest, we could start a Chip-in widget to add these features. I'd like to do that with an eye toward integrating with Update Status (perhaps meaning, since that's where it lives in Drupal 6, inclusion in core), so talking about this possibility with people involved with that module could be a very useful, non-tech role.
These are good suggestions, certainly in the spirit of Enabled Modules, and I will keep them in mind. What I've been trying to say is that on a technical level (in my current view and understanding) it makes more sense to implement them as patches to Update Status than as a separate module.
best,
benjamin, Agaric Design Collective
#2
Thanks for the feedback.
The module is very useful as it is.
My contribution will be limited to cheering from the sidelines, and testing patches, I'm afraid.
Later
Alan
#3
Which is great also!
#4
If we do anything it will probably be for Drupal 6 and something of a backport of this core patch proposed for Drupal 7 to add a text file export of the module status page: http://drupal.org/node/99529
Actually, this module should be replaced with one that uses Views 2 to make sortable lists of the modules to display any way you want.
benjamin, Agaric Design Collective
#5
With #762678: Expose {system} table to views coming along nicely, soon you'll be able to do the above (group by package) or differently (perhaps group by project) as you wish.
Plus, we can implement a default, but once it's done with views, you can always override this on a particular site without rebuilding from scratch.
#6
This is being done in #764350: Existing pages to be rewritten using views
#7
Done as part of #764350: Existing pages to be rewritten using views
#8
Automatically closed -- issue fixed for 2 weeks with no activity.