On node forms, hs_menu alters the menu.
This will clash with other modules that do so too. To name a few: http://drupal.org/project/og_menu , http://drupal.org/project/menuux , and probably a few more in D7. All those modules probably clash with each other ;)

A real use case I'm facing now:
A multilingual site, 4 menu's, menu-fr,menu-nl, menu-de,menu-en, a hierarchical select with the right config and patches (see: #1271386: Hierarchical Select Menu should respect menu_options) will make for a really nice and user friendly experience. Same site has a social feature, independent of language, and structured around private Organic Groups with organic groups content posted within. Users can add content and append it to a group specific menu, completely independent of the other site menu's. This is provided by og_menu.
As said before, og_menu will interfere with hierarchical select.

A simple solution would be adding a per-content-type setting on the hs_menu admin page. I can provide a patch for this which should be pretty much RTBC
As an additional motivation, I can perfectly imagine a use case where someone would like a Hierarchical Select on one content type and a Menu Browser provided by menuux on another type, this sort of flexibility is really an added value.

As I have recently taken on co-maintainership for the D7 branch for og_menu, I'm also interested in making it cooperate with hs_menu as it's a nice usability improvement. Do you have any ideas on this?

Thanks in advance.

W.

CommentFileSizeAuthor
#6 hs_menu_content_type-1271402-5.patch1.47 KBcyborg_572
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Wim Leers’s picture

Your use case sounds valid and your reasoning is solid. Please proceed as you see fit and I'll commit your changes :)

pinkonomy’s picture

Hi,
I am also interested in this,as on my site Hierarchical Select interferes with some module(s) and doesn't work.
Do we have any progress on this?
Thanks

rv0’s picture

A simple solution would be adding a per-content-type setting on the hs_menu admin page. I can provide a patch for this which should be pretty much RTBC

I'll have to manually apply that solution to the latest code, as the working HS where I used it also includes 3 other patches.
As soon as I find the time to do this, I'll post the patch here.

pinkonomy’s picture

Thanks for this,really appreciate.
Waiting for your solution

Wim Leers’s picture

Status: Active » Postponed

Updating status according to the progress here.

cyborg_572’s picture

Status: Postponed » Needs review
FileSize
1.47 KB

I know this is a 4 year old issue, I've run into this same problem recently, and had to patch it. This follows more-or-less what rv0 outlined in the feature request.

bzaher’s picture

I manually applied the patch on hs_menu 7.x-3.0-beta2 to work with og_menu 7.x-3.0 (https://www.drupal.org/project/og_menu), using the wetkit profile 7.x-4.1 (https://www.drupal.org/project/wetkit). This patch (#6) worked well. I can disable hs_menu for content types used by og_menu. Thanks for sharing.

stefan.r’s picture

Title: Prevent Hierarchical Select Menu from clashing with other modules. » Allow per content-type configuration of hs_menu
stefan.r’s picture

Status: Needs review » Fixed

Committed, thanks!

  • stefan.r committed 1c3535f on 7.x-3.x authored by cyborg_572
    Issue #1271402 by cyborg_572: Allow per content-type configuration of...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.