no documents on how to use this "vocabulary index"

Could you please provide some more info?
- What view are you using?
- Could you make a screen shot of the term hierarchy?

I have the same problem and described it in the german Drupal forum under the title "vocabindex-6.x-2.3 zerstört Inhalte" on january 11th and following days (URL: http://www.drupalcenter.de/node/24250). I can give summary of the important details in english - if required.

I noticed the failure after installing a new version of vocabindex; an error occured during the first run of update.php; everything looks very normal - except that "generic" URLs of the type http://domain/taxonomy/term/#number# point onto empty vocabularies. I have checked the date base tables (MySQL is used): those that are present look logical to me (however, I have no idea what the data model should look like) and no data seem to be lost (all information of term allocation ist present, but not used by drupal).

I could not figure out how the above mentioned paths are resolved by Drupal.

Hello,

I'm having the same problem with a fresh D6.15 install.

I have noticed that when the index page is of the type other than Browsable, everything works fine.

Xano:
- no views are involved.
- Taxonomie structure is fairly simple with only two levels:
Main-level1
-- sub-level1
-- sub-level2
Main-level2
-- sub-level1
-- sub-level2

We ran into an issue that sounds like the issue reported here.

We originally started off creating an index page that was in tree form. At that point, if you clicked on a term that had a node count greater than zero (has node that uses that taxonomy term), it would display a list of teaser for all of the nodes referencing that term.

We then changed one index to browsable. At that point, whether looking at the index that was in browsable or another that was still in tree form, if you clicked on a term that had a node count greater than zero, you would get the same no nodes found message that you would get for terms with node counts equal to zero.

We debugged this and came up with a solution. Attached is a diff/patch file. The base code was vocabindex-6.x-2.3. We use svn and don't check out of the official repository, so I am not sure if it can be applied as a regular patch. However, you can look at the file and see the diff and make the required changes.

Thanks .. that worked for me.

neubreed...
Any chance you could post your working vocabindex.module please?
Would love to have this working again but havent got time to go changing code.
Thanks in advance and thanks to the person that posted this issue... i thought id broken something lol
mikey

@mwhalen : For very short changes, Applying a patch manually is extremely quick and will save your precious time!
Certainly a million time quicker than asking someone else to do something and then waiting a few days to see if they will do you a favour.

- open patch.
- look at it.
- if it's less than a page (this is) then you may as well just :
- copy & paste the bit with [+] next to it into your file where the bit marked wit [-] currently is.
( [+] means add, [-] means take away. It really is that easy)
- remove the [+] characters from your file.
- save.

The hard bit there is figuring out how to copy and paste text from one place to another in your OS. If you can figure that out, the other part is easy.

Thanks dman
just thought it was a big complicated patch and as im on babysitting duties just wouldnt have time so went the lazy route, ;)
will fix it asap
thanks again everyone

Thanks that worked a treat!
(and was quite painless lol)

marcus_gbs thank you thank you thank you.....this was driving mental lol

I was having this same from problem on D 6.16 and vocabindex 6.x-2.3.

Downloaded the patch file from #4 and manually edited the .module file to make the patch. It fixed the problem.

I think you'd get more people to help test patches if there was a patched version of the module posted in the thread. Lots of us are happy to help but it's more than a lot of people have time or training to deal with to patch a module file.

I'm attaching the file I am currently using, renamed with an extra .txt extension that needs to be removed in order for it to function.

(How many good results does it normally take to move an issue to RTBC?)

I would call this critical, as not only does it limit the modules functionality, it removes the core functionality of the taxonomy module.

It was making me mental as well. I have found a non-code workaround, if I enable the Views Bonus view for taxonomy_term, the display seems correct.

I've applied this path and yet I am still experiencing this problem, as described in the first post. I have a single, very simple, two level vocabulary with about 40 terms.

I've tried uninstalling and reinstalling, thinking that perhaps VI works better when being installed over pre-existing vocabs... no dice.

jason

According to the project page, this project will be deprecated at some point, in favor of Index (http://drupal.org/project/index).

I can confirm verta's workaround (comment #13) of enabling the taxonomy_term View works. My hair pulling episode was a result of a difference between local and staging environments.

I happened to enable the 'bonus' taxonomy_term View locally whilst designing a view. Later I installed and configured VI and never had an issue. Though after install VI on staging, the term listing page was driving me bonkers.

Can anyone tell me if this is fixed in the dev release?

no documents on how to use this "vocabulary index"

Please don't hijack issues. This is extremely rude.
There is a README.txt file and the module displays instructions when it is enabled. If you still experience problems after that create a new issue and be specific about the problem you're experiencing.
Also note that this module is no longer maintained as it has the status Seeking new maintainer.

Hi Xano,

Sorry for being so rude, deeply apologize.

I did follow the instruction, but then I got lost, could you send me some instruction?

Thanks

Ruichen

Hi Xano,

I have got this worked!

But I wish that there is a place to modify the index page title.

Thanks,

Ruichen

Again, stop hijacking issues that are not about your problem.