Closed (won't fix)
Project:
Menu Rules
Version:
7.x-1.4
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Nov 2012 at 16:43 UTC
Updated:
5 Mar 2014 at 08:13 UTC
Jump to comment: Most recent
I made a patch for a problem of mine on a simple website. I needed the breadcrumbs to follow the main menu trail. But I did not want the corresponding entries to show in my main menu block as childs.
I added the option to hide the created/updated entry in the menu rules configuration. See the included patch.
I don't really now if it is of any interest for other case use, but as it was fairly easy to code, here it is.
Probably needs review, as I also added a test over an unrecongnized object data ($node->original) in case of a new entry creation.
Under both "add menu entry" and "update menu entry" rules actions there is now a last option to "hide the created entry"
none
| Comment | File | Size | Author |
|---|---|---|---|
| hide_entry.patch | 3.13 KB | defred |
Comments
Comment #1
ordermind commentedIt's a good idea, but I think it would be better if instead of a "Hidden" boolean which defaults to false, you would make an "Enabled" boolean which defaults to true, since that's what it looks like on a standard menu item form. That would make it more intuitive to users.
Comment #2
ordermind commentedNo update in a year it seems. If anyone feels like taking this on, please reopen the issue.
Comment #3
peterlolty commentedI need this...
Comment #4
ordermind commentedI repeat, if someone wants to take this on then please reopen the issue. That means whoever reopens the issue should attach a patch.