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.I wonder what exactly is the purpose of admin_views being shipped with admin_menu.
I don't see any technical connection between the two modules.
I think admin_views is cool, and maybe some people would miss it if it was not part of admin_menu. On the other hand, some people might miss the module exactly because it is part of admin menu.
Having it as a separate project would give us:
- less confusion in situations like "go install admin views". (obviously I am currently not confused, I know where admin_views is)
- separate ratings for admin_menu and admin_views on drupalmodules.com
- separate module description
- separate documentation
- separate usage stats
- separate issue queue
- separate version numbers and alpha/beta/unstable status (currently you need 3.x to get admin_views)
- etc.
Unfortunately, it will probably create havoc on sites that have both installed. Not sure how that could be solved.
Comments
Comment #1
sunComment #2
donquixote CreditAttribution: donquixote commentedOk, let it be admin_ux. Sounds good.
Comment #3
sunSplitted admin_views into http://drupal.org/project/admin_views
Comment #4
donquixote CreditAttribution: donquixote commentedThanks!
Comment #5
klonos...coming from Daniel's comment in #884032-26: Add enabled views to the 'Views' menu
@donquixote:
How about a new 7.x-4.x branch perhaps and a notice in the project's page? I'm sure that even then most people going from 7.x-3.x to 7.x-4.x would try an in-place upgrade (without fist deleting the 7.x-3.x folder) so a check in 7.x-4.x to see if there's still a admin_views directory under the parent admin_menu one would help communicate the change. If detected, you could through an error message like so:
"The Admin Views submodule previously included with Admin Menu has now moved to its own project. You'll need to:
1. Uninstall the old admin_views module [link to the site's modules page].
2. Delete the admin_views subdirectory from your admin_views installation."
The first task in the list would only show if the submodule is enabled.
The second task would go away once the subdirectory is deleted.
The text in the message could stay and change to a notice/warning (just to let people know of the existence of Admin Views), but I don't think it'd be that important anyways.
Of course we can also be completely inconsiderate and let havoc happen by throwing the "You shouldn't use dev or non-stable versions until they are a finished product." excuse at people coming in with complaints ;)
...I'm pretty sure we'll get a few extra issues in the queue if we go that way though.