It would appear that the Drupal 5 build can block access to content, but not hide menu items based on that block. Is this correct, or is mine just not working right?

If this is correct, would this module help me?
http://drupal.org/project/menu_per_role

Comments

Dave Cohen’s picture

Dave Cohen commented
Status: Active » Closed (duplicate)

A problem for many people. See these conversations:
http://drupal.org/node/16542
http://drupal.org/node/74826

brianpeat’s picture

brianpeat commented
Status: Closed (duplicate) » Closed (won't fix)

Those are all old posts (not for Drupal 5) and the hack in the second post actually breaks Druapl 5 completely.

hanskuiters’s picture

hanskuiters commented

I you just need terms in the menu, and not nodes, you can use taxonomy context. Just tested it with 5.0.

Dave Cohen’s picture

Dave Cohen commented

Regardless of the drupal version, this issue is not best solved in a node_access module. Hopefully the menu module can take hidden nodes into account.

brianpeat’s picture

brianpeat commented

I ended up using Taxonomy Access to hide certain nodes from certain users, and then menu_per_role to hide the menus from them.

If anyone knows a cleaner way to limit content by role and hide the menu item, I'm all ears. This works, it's just complicated when you're creating content and have a long list of role types (in my case, the roles and categories are actual school Class titles) to choose from and it can easily get cumbersome to work with. It seems so far to be the best option though. You can't search for the hidden content, and you don't have to fiddle with the menus, stuff you're not allowed to see just doesn't show up.

veeray’s picture

veeray commented

not sure if this is redundant or helpful. When limiting access to all terms, I would like the entire field to disappear from add/edit menus. instead the field remains with no available terms.