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.Simpletest is a development tool, not a site building tool. And we have schema and devel modules (possibly others, no offense to them) in core. To reduce confusion for new users who install Drupal 7 and enable SimpleTest, and to reduce potential naming conflicts if development modules add their own top level items (I think schema adds a 'database' package name now), let's add a new top level item.
I'll look a bit empty if only simpletest is enabled, but hopefully the number of sites running simpletest in production will be 0, and the number of sites running simpletest without also having devel installed should be 0 as well.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | devel_menu.patch | 4.44 KB | catch |
| #2 | devel_menu.patch | 3.27 KB | catch |
| #2 | devel_generate.patch.txt | 2.23 KB | catch |
| #2 | Screenshot-Administer | d7.7 - Mozilla Firefox.png | 60.94 KB | catch |
Comments
Comment #1
stella CreditAttribution: stella commented+1 for this
Then the new merged coder + deadwood module could live here too.
Comment #2
catchwebchick mentioned in irc that we don't currently have a good way for optional modules to all use the same top-level menu item, however I just added the same entry to both simpletest and devel, and it works fine (I think the menu system just overwrites in the menu_router table).
So here's a patch - one for HEAD, just to move simpletest out of site building, and one for devel generate to prove it works like this.
NB, this will break tests - it's mainly so people can see how it looks.
Comment #4
catchProper patch with conversion of all paths (unless there's some references outside simpletest.module)
Comment #5
dmitrig01 CreditAttribution: dmitrig01 commentedThere sholud be some better solution - we shouldn't have to make all modules that define things under admin/content have to define admin/content and so on and so forth for the other paths.
Comment #6
sunI agree with dmitrig01. Panels 2 - and modules integrating with Panels - suffered from this lack. We (really) do not want each and every module to register and define the same top-level menu item all over again.
We need a new layer (or menu item type) in the menu system that allows to wrap sub-items, or in other words, categorize menu trees.
Comment #7
Dries CreditAttribution: Dries commented#5 and #6 are valid but requires its own issue/patch -- it is a separate but related discussion.
Comment #8
catchYep, the IA the the admin screen and the limitations of how to put items into it are separate discussions.
Comment #9
Dries CreditAttribution: Dries commentedI think it is actually a feature that it is somewhat hard to create a new top-level menu item. If it were easy, we'd have 25 of them by now. ;)
I've committed this patch to CVS HEAD. Let's create a new issue to discuss menu system improvements.
The easiest solution is probably for other modules to create a dependency on SimpleTest. That could be a smart thing in our quest to get more people to write and run tests.