Menu items always visible

subscribing (feature request?)

This is a Drupal limitation (or feature). It looks like Drupal does not allow pulling menu links for nodes that user does not have access to.

These are the options I can think of:
1) Deal with it.
2) Hard-code the menu links in your template. This is not a good solution if your menu needs to be dynamically populated and requires the Drupal menu features.
3) Hack approach. Copy and rename the Drupal menu functions (menu_navigation_links(), menu_tree_page_data(), menu_tree_check_access(), _menu_tree_check_access(), and _menu_link_translate()) and modify them removing the code where it does menu item access checks (if ($item['access']) {). Then you can use the new functions for your needs. However, remember this is a hack. Who knows if this may break with a newer Drupal version.
4) Create your own function for pulling menu links.
5) Implement a different access_content module. It would behave similarly to this one, but it would not use hook_node_access_records() for setting node permissions.

This would be a very useful feature. Show restricted items in menu.

Has anybody found a solution for this problem or not?

I don't know why is this feature ignored in the drupal community. Everyone needs it, but still ignored.

I would like to know too :)

It is so easy, you don't need to install or learn to something to do it. Just create a new Menu item and give full URL in path field now this menu will be visible whether content is restricted or not.

Full URL:http://drupal.org/node/724978" not like this "node/724978".

You can also use this module for better solution:
https://www.drupal.org/project/always_visible

You could also allow restricted users to see titles and teasers only, but not full nodes using Premium

It is so easy, you don't need to install or learn to something to do it. Just create a new Menu item and give full URL in path field now this menu will be visible whether content is restricted or not.

Full URL:http://drupal.org/node/724978" not like this "node/724978".

1) This solution adds additional manual work. For each node that you create or delete, you need to create or delete a menu item separately from the node (on a different page). If your node path depends on menu title, you need to update the path alias manually, too. This may be easy and fast for you. But it could be time consuming and annoying for someone else.
2) With this solution, the breadcrumbs are not set if they depend on the menu.
3) If you move to a different domain address, you would need to update all your menu links with absolute paths.
4) If your site is located at multiple domain addresses, good luck managing all your menu links with absolute paths.

Bump.

See also: http://drupal.org/node/723964 and http://drupal.org/node/300607

I'm sorry to spam this thread, but I made a sandbox project of out my solution: http://drupal.org/sandbox/mthomas/1119418

Thanks for the sandbox module! It's works great.

It's out of the scope of this module, I guess you either use mthomas' sandbox or wait for the entity access module which will cover it AFAIK.

#13 worked for me!

I confirm #16, thank you for your work mthomas :)

Thanks a mil mthomas!

YOU ARE A LIFE SAVER

THANK YOU SHAFQAT - THIS WAS SO EASY :d

@shafqat1982, YOU'RE THE MAN!

This was an excellent suggestion as I only needed this for one simple create content link. Then i can use rules to redirect my users to login to submit this content.
Thanks shafqat1982

Solution #8 worked for me.

Thank you!

Thank you mthomas it's work!