The admin menu has some collisions with wildcards. It would be good to fix this, and other (contrib) modules could see the right way, how to create their menu structure. This collision is problematic, and fixing it with blacklisting is not the right solution.
if you unsure what should be fixed run this select:
SELECT mr1.path, mr2.path
FROM menu_router mr1, menu_router mr2
WHERE mr1.path <> mr2.path
AND mr1.path LIKE mr2.path
AND mr2.path <> LEFT ( mr1.path, LENGTH (mr2.path) )
There should be a document which describes how to create correct menu structures. The easy rule: do not use a wilcard on the same menu level where you have a normal menu item. With such document we could avoid issues like these:
#204415: Creating content types 'add', 'theme', 'list' (and possibly others) causes various problems
#180316: fix project/mymodule URI insanity
Other thing. I do not like the menu-customize item. I see it simply as a menu level pollution. It should be changed to menu/customize.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 220407-2-filter_format.patch | 19.21 KB | pasqualle |
Comments
Comment #2
pasquallesome of the issues fixed in: #508570: Restore URL consistency for node types and menus
lets continue with input formats
Comment #3
sunThis is not required for menu paths that use dynamic arguments which are integers. It only applies to arguments that are strings. If it is using integers, then the menu system will already figure out the proper callback to invoke, see {menu_router}.fit.
Hence, this is not required for filter.module.