Here a patch to make this module work with Taxonomy Menu.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | screenshot.png | 10.58 KB | jjcarrion |
| menu_firstchild-taxonomy_menu.patch | 1.15 KB | dcoulombe |
Here a patch to make this module work with Taxonomy Menu.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | screenshot.png | 10.58 KB | jjcarrion |
| menu_firstchild-taxonomy_menu.patch | 1.15 KB | dcoulombe |
Comments
Comment #1
anrikun commentedIs this really necessary? I'm not sure.
In what case may a Taxonomy Menu item have <firstchild> as path?
Comment #2
dcoulombe commentedIn my case it was very useful (it would be long and complicated to explain). On the other hand I understand your point, but why not allow taxonomy menu to work with menu firstchild?
Comment #3
anrikun commentedHi again dcoulombe.
It is not a matter of allowing taxonomy menu to work with menu firstchild: I'm ok with that :-)
It's just that I don't understand why a patch would be necessary for taxonomy menu to work with menu firstchild?
Doesn't they work well together in the current state?
So could you please explain your case? (even if it's a bit long and complicated ;-)
Comment #4
yoran scholiers commentedTaxonomy Menu does not allow you to change the path.
I have not tested this patch, but it stands to reason that it allows you to change the path.
Comment #5
jjcarrionI have tested this patch, but I don't see any differences. I'm using taxonomy_menu and as you can see in the screenshot atached, I cannot edit the path in the menu item neither in the taxonomy term.
Is there any posibility to use menu_firstchild with taxonomy_menu?
Thanks in advanced.
Comment #6
chris matthews commented>> Changing status to Needs work