Module for adding a custom path for the vocabulary only inserts garbage chars (%252F) before the vocab name.
jptaranto - April 5, 2009 - 07:48
| Project: | Taxonomy Menu |
| Version: | 6.x-2.4-beta1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
Seeing as I use views or other such methods to create a functional path for a vocabulary, the default taxonomy/term/1 2 3 4 behavior of Taxonomy Menu didn't quite suite me.
Using two of the new hooks from 6.x.2.3 I pieced together this very simple module which adds a field to the edit Vocab screen, much like the Taxonomy Menu Custom Path module does, which allows you to enter in a custom path for each vocabulary. Term paths are still treated exactly the same, so the path you enter only effects the vocab.
I've uploaded it, just in case anybody is interested or looking for that functionality.
| Attachment | Size |
|---|---|
| taxonomy_menu_vocabulary_path.zip | 1.54 KB |
#1
#2
#3
Thanks jptaranto. I'll take a look at it.
#4
Thank you! this is exactly what I needed! It is working perfectly on my site.
#5
just perfect fix for my problems :)
#6
Thanks for the module!
We want to have a view set up with the same base path as the taxonomy vocabulary custom path, so I added an option to just use that as the prefix instead of what taxonomy_term_path gives us (taxonomy/term/tid). In our case we are using the name not tid so we get customvocabname/termname if the new option is selected.
I am uploading here in case anyone else wants to use their own paths for the menu items (and hopefully this will make it into further releases). This is jptaranto's original vocab module plus my change to add a checkbox.
#7
Issue merged with #356281: Custom menu titles
This need to be turned into a path and fit in to the current taxonomy menu structure.
#8
I'm glad it's been of use to people! Warm fuzzy vibrations all round.
#9
just great this solved my problem
#10
Create Work. I'm adding #6 to the next release. Would you be able to do a little write up for the readme? Something about when to use this path and what id does. A use case would breate.
#11
Added to 2.4-beta1.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.
#13
This is a great addon!
However it looks like it works only with paths created in views.
I need to place only blocks on page, so I created empty page (Create content > Page) I've set path to 'demopath' and then I've putted this path in "Custom path for vocabulary: " on taxonomy menu configuration page, unfortunately my menu didn't show up.
Is it by design that it works only with views or it's a bug ?
#14
When menu items are attempted to be created, the menu system check to see if the page exists. If the page does not exist, then the menu item is not created. It doesn't matter where the paths are created.
What are you trying to do?
#15
Using this module as I think it's supposed to be used (but without documentation really addressing the use of this new feature), I'm getting a taxonomy menu generated at my base path ("blogtag") with extra characters in front of the term vocabulary name. For example, "Music" becomes "/blogtag/%252FMusic", which of course produces a page not found error when clicked. Any else having this problem?
#16