I can't find where is the slash added in the code, the patch just removes trailing slashes from generated paths.
| Comment | File | Size | Author |
|---|---|---|---|
| taxonomy_menu_path_custom.no-slash.patch | 398 bytes | joanpc |
I can't find where is the slash added in the code, the patch just removes trailing slashes from generated paths.
| Comment | File | Size | Author |
|---|---|---|---|
| taxonomy_menu_path_custom.no-slash.patch | 398 bytes | joanpc |
Comments
Comment #1
indytechcook commentedWell, taxonomy_menu_path_custom_path creates the path but it shouldn't be. Just removing the trailing slash may be covering up another bug.
What settings you you have for "display descendants', "Display depth in custom path", "Use term name", "Base path for custom path"? All of those seetings effect the path created for the custom path setting.
Comment #2
indytechcook commentedComment #3
joanpc commentedI have Display depth in custom path empty i don't understand what this field do :/
and checked:
Use term name
Synchronise changes to this vocabulary
Hide empty terms
Add item for vocabulary
Auto expand menu items
and
Use 'all' at the end of URL
thanks
Comment #4
indytechcook commentedIf you turn off "Use term name" what happens?
FYI, "Use 'all' at the end of the URL" only works on the default path type :)
Comment #5
joanpc commented/tea/4%209%202%205%206%203%207%208
/tea/4 9 2 5 6 3 7 8
in my tea menu :)
Comment #6
joanpc commentedI use the module to generate a menu for browsing taxonomies with a custom view.
ex:
/tea base path (view without arguments) -> show all teas
/tea/white-teas -> show teas with the white-teas term
/tea/chai-teas ...
ok, now i think I understand.. I'm using a bug of the module as a feature? The module should be listing all the term names after the /tea/ ?
we can convert the issue to a feature request :)
Comment #7
arlinsandbulte commentedThis issue has stagnated after more than 2 months at "postponed (maintainer needs more info)"
I'll mark as "won't fix"
Feel free to re-open...