Hierachical Select broke every module that restrict permission on menu?!

Impossible.

HS only alters forms. It doesn't do anything special to menu items.

It just can't be triggered by HS itself. Sure, it can be triggered by other modules.

Can you reproduce this on a vanilla Drupal site? If you cannot, keep on adding modules that you're using on your actual site until the problem is reproduced.

When you're able to reproduce this (on a vanilla Drupal site with the minimum number of modules to reproduce it), then please make a screencast of:

1. your site configuration
2. the problem being reproduced

That makes it easier for me to reproduce the problem. Thanks!

P.S.: don't have any screencast software yet? On Windows and Mac OS X, you can use the free Jing.

Is it possible to fill in the menu items dynamically? Lets say by reading a table in DB.

Thanks

@tomvolek: are you asking for a feature? This is not a feature request but a problem report.

Hi Wim,

i think sistro is right. The modules "menu_admin_per_menu" and "ctm" do not work together with "Hierachical Select".

I have configured testsystem with only four modules:

- Drupal 6.16
- Hierarchical Select 6.x-3.0
- Menu Settings per Content Type 6.x-1.0 (http://drupal.org/project/ctm)
- Menu Admin per Menu 6.x-1.3 (http://drupal.org/project/menu_admin_per_menu)

There's two roles (admin & editor) and two users (Mr. Admin & Mr. Editor)

1) First Setup - Only Hierarchical Select activated
Modules active: Only Hierarchical Select, Hierarchical Select Menu
Permissions: authenticated user -> administer menu
Everything works fine. Mr. Editor can create a page and the Menu settings uses hierarchical select. All menus are available in the menu drop-down

2) Second Setup - Only Menu Settings per Content Type activated
Modules active: Menu Settings per Content Type
Permissions: authenticated user -> administer menu
Settings: Only "Primary Links" checked in the menu setting at the content typ "page"
Everything works fine. Mr. Editor can create a page an only the menu "Primary links" in normal drop-down style is available.

3) Third Setup - Hierarchical Select & Menu Settings per Content Type
Modules active: Hierarchical Select, Hierarchical Select Menu, Menu Settings per Content Type
Permissions: authenticated user -> administer menu
Settings: Only "Primary Links" checked in the menu setting at the content typ "page"
Almost Everything works fine. Mr. Editor can create a page and the Menu settings uses hierarchical select. But not only the menu "Primary links" are there, but also the other menus (primary, secondary, naviagtion, development)

4) Fourth Setup - Menu Admin per Menu activated
Modules active: Menu Admin per Menu
Permissions: editor -> administer primary-links menu items, administer secondary-links menu items
admin -> administer devel menu items, administer navigation menu items
Everything works fine. Mr. Editor can create a page and there's only the primary-links and secondary-links available in the menu drop-down. Same thing with Mr. Admin: he has only development and navigation menu items.

3) Fifth Setup - Hierarchical Select & Menu Admin per Menu
Modules active: Hierarchical Select, Hierarchical Select Menu, Menu Admin per Menu
Permissions: editor -> administer primary-links menu items, administer secondary-links menu items
admin -> administer devel menu items, administer navigation menu items
Almost Everything works fine. Hierarchical Select Menu is not working with the roles "editor" & "admin". Mr. Editor can create a page and there's only the primary-links and secondary-links available in the menu drop-down. Same thing with Mr. Admin: he has only development and navigation menu items. Hierarchical Select is working with User #1, with all four menu-trees.

I've tried a few things (setting the weight of the other modules for ex.) but i didn't find a solution. i attached the DB of my testsystem.

Du you have an idea?

Thanks, Franzer

Aha, you're talking about the menu settings on the *node form*!

- Menu Settings per Content Type - http://drupal.org/project/ctm
-> will work when its module weight is adjusted to run *after* HS Menu
- Menu Admin per Menu - http://drupal.org/project/menu_admin_per_menu
-> probably the same
- Delegate Menu Administration - http://drupal.org/project/delegate_menu_admin
-> is likely impossible to get working with HS Taxonomy

Note that all of this is due to the internal mess of Drupal and not due to HS or any of those modules. No module is to blame: core is!

This issue is fixed since HS can't change anything: it's the other modules that need to be adapted (unfortunately).

I tried setting Menu Settings per Content Type module weight to run after HS menu, it still doesn't work.

Just wanted to set this active again. Hopefully these two modules can be made to work together, they would make a great combination for allowing users to set menu settings on a node.

Subscribing.

I'm not going to fix this. HS does the menu form item altering correctly. Please ask in the problematic menu modules for help/compatibility. I've solved many dozens of compatibility issues already. Sorry, and thank you for your understanding.

As far as I'm aware Menu Settings per Content Type - http://drupal.org/project/ctm will part of Drupal 7 core.

Not sure if this has any bearing on this topic.