Jump to:
| Project: | NodeSymlinks |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | postponed |
| Issue tags: | multiple menu locations, navigation, user experience |
Issue Summary
Symlinks are great and I love this approach, but there are times you don't want a page to actually exist in every location it occupies within the menu hierarchy.
I propose including a "Redirect" column with a checkbox for each additional location added under 'Menu Settings'. If the box is checked, then selecting that menu item will redirect you to the base location for the node, much like the Multiple Node Menu module behaves. If you don't check the box, then the menu item will behave like a symlink, as it currently does.
I have many use cases for this, but here is one example. I'm working on a website with an "Event Services" node. This node needs to be listed in multiple locations within the primary menu hierarchy—and NodeSymlinks works well for that—but the node also needs to be listed in the footer menu at the bottom of every page. When someone clicks on the "Event Services" link in the footer menu, I want them to be redirected to the node's base location under the primary menu. I don't want anything to actually "exist" in that footer menu.
Comments
#1
I think these two modules does two different things and as far as I know there is no conflict between them, so you can use them both - exactly in the way which you described.
Maybe I will integrate it in the future, but for now is it low priority for me.
#2
I'll have to do some testing to see how well these modules work together, but the fact that they can work together doesn't mean that they should. Having multiple interfaces for menu management seems like poor interface design to me. Having one interface that can handle both symlinks and redirects would make for a much improved user experience. I hope you will consider this in the future.
#3
I made a try couple days ago. It works, but you are that combination of these two UIs isn't nice... (mainly because of little bit strange Multiple Node Menu adjustments of the node menu form)...
Problem is that this "new feature" needs to rethink & rewrite whole UI and backend. It is basically integration of two modules, two concepts under one UI.
I'm considering this for the Drupal 7 version of the module.
#4
Has there been any movement on this module? I could really use this sort of functionality on my site as the current version picks the wrong menu when going to pages that have multiple locations in my menu.