I consider myself a decent Drupal-er, but using this module has me stumped. I'd be happy to document something, if I had any clue how to use the module.

I've created a node view and was going to add the term field, as stated in the README, however it says in the view config that fields are not allowed with this view type. Also, not sure what to enter in the Vocab to use field. The name and ID both don't work.
So, then I decided to try making a vocab view, but that doesn't work either, and wouldn't have let me filter by what would have been in the view... which is the whole point of the module.

Feeling dense.

CommentFileSizeAuthor
#5 613220.patch526 bytesstella
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

valderama’s picture

:) same prob. i 'll let you know if i find out how to handle this module...

witzel’s picture

I also can't figgure out how to create a cloud view with tagadelic. What is the difference between this module and the views cloud module?

bones’s picture

Was having the same issues, found that it doesn't work with a space in the vocab name. You need to put the vocab name in the vocab to use field.

doublejosh’s picture

Put my single word vocab name (which I guess is from the vocab title?) and it still "Could not find tags!"

stella’s picture

Title: Even just creating a view... totally stumped. » No fields allowed for this view
Category: support » bug
Status: Active » Needs review
FileSize
526 bytes

The attached patch addresses the problem of the fields not being allowed for the view when the tagadelic style is selected. Currently you need to select the fields to use before you set the view style to be 'tagadelic'.

Ideally the 'vocab' options form should be a drop-down or set of checkboxes as currently it's not that usable. This does work however - you just need to enter in a comma separated list of vocab names. I'm not sure what will happen if you have a comma in your vocab name, as using quotes doesn't seem to work. At the same time, I don't think this option is really needed as you can just use the normal filter options to achieve the same effect.

doublejosh’s picture

My problem was actually caused by Page Title. It was getting it's title value too early (from token cache) and never letting the view set the title. Fixed in version 6-2.3

http://drupal.org/node/529186