Last updated by roderik on Tue, 2010-09-28 23:50
Comparison of Menu settings modules:
- Auto Menu Title - auto-populates menu title per content type (no option to auto-populate with checkbox confirmation like in D7 core)
- Auto Menu - auto-populates menu title (didn't got it to work) per content type
- Simple Menu Settings - adds a checkbox to enable menus at content type creation/edition; auto-populates menu title per content type
- Node Menu Parent - sets the default parent menu per content type
- Menu Settings per Content Type - allows choosing menus parents from selected menus per content type
- Menuless Node Type - removes menu options per content type (obsoleted by Menu Settings per Content Type)
i can confirm Menu Settings per Content Type works with Node Menu Parent.
Menu Settings per Content Type works with Simple Menu Settings if you give the former module a higher weight than the latter. (UPDATE system set weight=1 WHERE name='ctm')
how about a common effort to merge all of these into a single module, performing all of the functionalities above and mimicking Drupal 7 core behaviour, as if it was a backport?
additionally, there could be an option to autocreate menus always for a given content type, as Auto Menu Title does it.
this way i think all users would be happy and there would be less confusion around... 6 modules into 1.
i'd say, pick Menu Settings per Content Type (ctm) and start work from there.