Clicking parents in term trees doesn't show term pages
soliaris - September 8, 2008 - 07:34
| Project: | Vocabulary Index |
| Version: | 6.x-2.0-beta1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Xano |
| Status: | by design |
Jump to:
Description
Hello,
I have terms and subterms in my taxonomy.
for example term1, 2, 3 are main terms, and term 4,5,6 are belonging to parent term1. I have tried to used vocabulary index to display menu for taxonomy terms. I have tried both setups page and block. In both cases subterms 4,5,6 are displaied correctly as menu items, but paths are wrong. I would expect paths like taxonomy/term/4, taxonomy/term/5 and taxonomy/term/6. Instead paths are taxonomy/term/3#. And this is for parent term1 and for subterms 4,5,6 - same patf term/3#.
If I am not using hierarchy and no subterms for term1, than everything is ok.
Is it known bug or I am doing something wrong.
Best regards
Soliaris
#1
It looks like you're using another Taxonomy-related module that modifies term paths. Vocabulary Index doesn't modify any part your system and lets Drupal generate the term paths.
#2
Hi again,
Taxonomy/term paths in Drupal are correct. I am saying menu block or page (depends on vocab index setup) which are direct responsibility of vocabulary index are pointing to wrong paths.
Lets say my taxonomy term names are countries. Lithuania, Latvia and Estonia. Lithuania has two subterms Republic before WWII and current republic.
So Vocabulary index is displaying (in menu block or in page):
Latvia,
Estonia,
Lithuania
I am clicking on Latvia, and menu system gives me taxonomy/term/3 page with all nodes. Ok.
I am clicking Estonia, and menu system gives me taxonomy/term/2 page. Ok.
I am clicking Lithuania, and menu system shows two subterms (I am using tree setup). And I am clicking subterm one or subterm two. Boths are redirecting to taxonomy/term/3# path which does not exist. That is not ok.
I have even tried one more thing. Added one more country and one subterm. So same result. Vocab menu system or page redirects to same path taxonomy/term/3#.
So I think this is exactly vocabulary index problem. In my current installation there are no more modules related to taxonomy, I have uninistalled and removed everything.
shall I do clean install and try it again?
#3
One more comment:
This is true for activated JavaScript to gracefully expand term trees.
Regarding wrong paths I have noticed such strange behaviour. If I am pointing to expanded java script tree menu item, it always shows path like this:
#
For example I have opened admin. After I am clicking on menu item Lithuania to expand Lithuania subterms. Path is shown like Lithuania#. So it seems something is wrong with JavaScript wich opens menu tree, and not providing correct path to subterms.
In all other configs everything perfect.
#4
That's normal behaviour. Term trees with JavaScript enabled will not allow users to visit terms that are parents, simply because this is necessary for the JavaScript to function. If users would be allowed to visit those term pages from the tree, the tree wouldn't be able to expand since a new page would be loaded. Solution: disable JavaScript through the Vocabulary Index settings page.
#5
#6
Hello,
One more question regarding this. I do not know what has been changed since beta1, but now paths generated by javascript enabled are correct. But still one problem exists - i am not able to open menu generated by javascript by mouse click. It is possible to open only in case of right mouse click and then to choose open, or open in new window.
Could you please check this? I am using latest dev version now.
Best regards,
Soliaris
#7
1) Vocabulary Index does not create menus.
2) If you're referring to tree views, they're not created by Javascript. JS is only being used to expand parent terms so their children are shown. By clicking a parent term with your primary mouse button (left for right-handed people) you are not going to it's Taxonomy page, but its children are being collapsed instead. They're ordinary links, so right click > open isn't possible. Right clicks trigger your browser's default behaviour.
#8
Hello,
maybe my explanations was not clear enough, but anyway you fixed it by:
http://drupal.org/node/322070
BR,
Soliaris
#9
Technically it was a different problem, but from an end-user point of view I understand they are similar.
#10
(Double post)
#11