Two bugs and two feature requests
| Project: | Vocabulary Index |
| Version: | 6.x-2.1 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Bug #1
Description of Bug: Navigation links are the little links that can help one go backward and forward in an information hierarchy such as the taxonomy. For example, Home > Parent Term > Child Term 1 With Vocabulary Index this doesn't work
What are the steps required to reproduce the bug?
1) Create a vocabulary "Location" with 3 levels, say country > state > city as in United States > New Mexico > Albuquerque
2) Associate the vocabulary with a content type.
3) Create a URL for the vocabulary in admin/build/vocabindex/pages say "/location" View = browsable, Node Counts =checked
4) Go to the page /location the says "Home"
5) Click on United States, the navigation still says "Home"
6) Click on New Mexico, the navigation still says "Home"
7) Click on Albuquerque, the navigation now says Home > United States > New Mexico
What behavior were you expecting?
Why does it not say Home > United States in 6)?
What happened instead? See 6) above.
There seems to be no way to navigate backward in the directory without using the back button on the browser.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Bug #2 URL issues - The modules doesn’t seem to respect pathauto or the URL I add at admin/build/vocabindex/pages
What are the steps required to reproduce the bug?
1) Create a vocabulary "Location" with 3 levels, say country > state > city as in United States > New Mexico > Albuquerque
2) Associate the vocabulary with a content type.
3) Create a URL for the vocabulary in admin/build/vocabindex/pages say "/location" View = browsable, Node Counts =checked
4) Go to the page /location, the URL works great it’s http://www.mysite.com/location as it should be.
5) Click on United States.
What behavior were you expecting? The URL to be http://www.sites.com/location/united-states
What happened instead? The URL is http://www.mysite.com/category/location/united-states
I have pathauto set to remove category but the module doesn’t seem to obey that or the base URL I created in the admin at lower levels of a taxonomy hierarchy.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
This is feature request #1 or possibly bug #3 depending upon one’s frame of mind.
The number reported in the Node counts includes both the number of categories plus the number of nodes. It would be better if it only counted the number of actual nodes.
1) Create a vocabulary "Location" with 3 levels, say country > state > city as in United States > New Mexico > Albuquerque
2) Associate the vocabulary with a content type.
3) Create a URL for the vocabulary in admin/build/vocabindex/pages say "/location" View = browsable, Node Counts =checked
4) Create a content node using the aforementioned mystery content type and assign it a location, Albuquerque, New Mexico, United States.
5) Go to the page /location
What behavior were you expecting? To see United States (1)
What happened instead? It shows United States (3)
6) Click United States
What behavior were you expecting? To see New Mexico (1)
What happened instead? It shows New Mexico (2)
Here comes the feature request… create a place in the admin where the admin can choose Node counts [ ] and/or Category counts [ ] as some webmasters may want to report the number of nodes while other might want the number of categories, but I doubt many will want both summed together.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Feature request #2
Create a Vocabulary Index language page that displays all the Vocabularies you have chosen to index. Right now, there is no option to create a Vocabulary Index Landing Page or to select the vocabularies you want to use in a straightforward way (I guess you do it now by not assigning a URL?)
An associated feature request would be to keep in mind Bug #1 so that if this happened, the navigation links would be Home > Directory > Parent Term > Child Term 1 etc..
One very nice way to do it is to actually show the last item in the line, but deactivate the link as in
Home (link) > Directory (link) > Parent Term (Link) > Child Term 1 (Link) > Child Term 2 (no link, just text) so users will know exactly where they are in the navigation.
Anyhow, I’d like to thank you very much if you took the time to read to the bottom of this long text. I really like the directory as it is but if you are able to fix/add these things, I think you’ll be able to make this the best directory option for Drupal by far.
If you could make it work with CCK / Content Taxonomy fields, that would be even better!
Thanks for the nice effort.

#1
Thanks for reporting these bugs! Could you please post them in separate issues? Also, new features are never added to existing versions. Since Index is Vocabulary Index' successor, new feature requests belong there.
Note that node counts are done by Taxonomy and not by Vocabulary Index (as you can find elsewhere in this issue queue). What you describe is a known bug in Taxonomy, I just don't know if it has been fixes yet in newer versions of Drupal 6. Breadcrumb support has been deliberately left out in favour of Taxonomy breadcrumb.
#2
Hi, Xano! Can you put same example of use Vocabulary Index with Taxonomy breadcrumb, btw? I can't start they work together (http://drupal.org/node/472068).
Thank you.
#3
Sure, I commented in the other issue. Let's get the problem fixed over there :)