Refinement documentation
temp - September 17, 2009 - 18:30
| Project: | Taxonomy Menu |
| Version: | 6.x-2.4-beta1 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | temp |
| Status: | by design |
Jump to:
Description
"Synchronize changes to this vocabulary:" what is the difference from "Select to rebuild the menu on submit:" in both cases (as I understand it) refers to rebuild menu on the basis of terms dictionary.
The easiest way to understand for example - in which case I need to use the "Select to rebuild the menu on submit:"
"Custom: Creates a custom base for each vocabulary. Useful if you would like a different path or view for each vocabulary. See the 'Views' section below for more information about views." Sorry, but i do not understand this setting, I also can create several dictionaries and for each of them set up their taxonomy_menus with the "Default Menu Path Type" this right?
thanks for great module - sorry for questions! =)
#1
Sorry, change Issue title: to Refinement documentation
#2
"Synchronize changes to this vocabulary" updates the menu when when a the vocabulary term tree is changed or if you have the show node count option selected, then it updates when a term is associated or unassociated with a note.
"Select to rebuild the menu on submit" deletes all of the menu items from the menu and from the taxonomy menu tables, then recreates them. Useful if you are having issues.
There are different path types. If you select "Custom" some of the options will effect the creation of the path. I know this is a little confusing, in the next major release, only the options for the specified path will display.
Yes you can. It uses the default taxonomy path of taxonomy/term/tid. This is the only one 100% compatible with only core. The require views or a custom menu callback.
#3
Thank you for your answers, they helped.
Just everything is very confusing with different path types.
Why not simply make the choice:
1 of the parent menu,
2 and under him the field with template for the path, based on the token module.
#4
temp, tokens weren't used because they were not part of core. This module is only going to rely on core.