Great module! I need to quickly get menus with taxonomy, and the Taxonomy Menutree plugged right in and had a lot of useful options for adding menus. I like the way it is designed and integrated with the menu administration.
I did face a situation where I wanted to disable a parent term, but still wanted the child terms listed. It would be nice, if by unchecking Enabled while leaving Expanded checked would simply omit the parent item (thus adding the parent's item children to the same level of the parent).
Item Enabled Expanded ("x" means checked, "-" means unchecked)
+ Parent_1 - x
++ Child_1_1 x x
++ Child_1_2 x x
++ Child_1_3 x x
+ Parent_2 x x
++ Child_2_1 - x
+++ Grandchild_2_1 x x
+++ Grandchild_2_2 x x
+++ Grandchild_2_3 x x
Should ouput:
+ Child_1_1
+ Child_1_2
+ Child_1_3
+ Parent_2
++ Grandchild_2_1
++ Grandchild_2_2
++ Grandchild_2_3
This would mean that to disable an item completely you must uncheck both enabled and expanded.
Thanks in advance!
Comments
Comment #1
rcrowther CreditAttribution: rcrowther commentedHa Hah! You're ahead of me!
First up, thanks for posting a detailed comment - I got you straight away, and that's a help.
I've not really addressed the issues of expansion, and what might be called 'inheritance' of properties. I made a snap decision a couple of months ago to make all menus expanded by default, and to disable all menu movement. That way the menus always reflect the taxonomy, and the taxonomy has to be moved to move a menu. And dropped the issue right there.
At base, this a feature request, and a really interesting one. The problem is, I saw the possibilities a few weeks ago, and I've worked hard on getting good useful options in, and getting them into a format that works for users. I've spent the last week updating the Taxonomy Router. When I get back to Taxonomy Treemenu itself, I've got a couple of deep issues to cover (node handling is a bit heavy on the links table, caching is not enabled). Oh, and there's another module yet to be released, for 'intelligent' blocks.
I suppose I'm saying, until and unless we get other coders on board, you'll have to live with my pace.
I'll leave this one open, though, cause it's groovy!
Rob
Comment #2
jptaranto CreditAttribution: jptaranto commentedAha! Just what I had requested. Oops.
Comment #3
lee20 CreditAttribution: lee20 commentedThis is a duplicate of: #345590 Hide parent item.
@jptaranto I just noticed you had only beat me by 3 minutes!
Comment #4
lee20 CreditAttribution: lee20 commentedI had to to use the Menu block module which has pretty good capabilities for extracting various layers of any menu. I haven't tried it in combination with Taxonomy Treemenu but I would expect them to work together.
Just wanted to mention the Menu block module as a possible alternative to customizing your Taxonomy Treemenus!