Jump to:
| Project: | Tagadelic |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
any ideas? willing to work with this code, but it would need to updated for d6 (the first section up top, which focused on only selected vocabs) http://drupal.org/node/157802
situation (example) - content type 'providers' with categories 'restaurants, babysitters, etc' - within each node user is required to select from a drop down list (e.g much choose 'restaurant' or 'babysitter' or other top level directory category) AND may enter assorted 'free form tags' (e.g. italian food, pasta, yummy etc)
when block is enabled for content type "providers" it now only shows the top level categories as 'tags' in the cloud (restaurant) and not any of the free form tags (italian, etc) even if within a category page like 'restaurants' (content/provider-categories/*)
any ideas why this is happening or how to get it to show the free form tags???
Comments
#1
have i possibly configured this all wrong? or is this just not possible for tagadelic (ignore fixed vocab and instead use just free form tags)? thoughts? anybody?
#2
I have the same problem.
#3
believe i've figure out two resolutions...
one is views tagadelic, though it's a bit nerdy (create a tagadelic view and constrain to terms)
the other is to simply create a new 'free tag' vocabulary and assign to the content type - this is a bit more tedious and doesn't actually solve things completely (e.g. all 'providers' are lumped into one tag cloud with its own free tag taxonomy - so if i hit a restaurant i also see tags for other top level cats like clothing stores) alternative is to create a free tag for just 'restaurant' - and that's okay, and it WILL work for the tag cloud issue i'm describing, but it is tedious if you have many terms to handle (in this case i have only 7 so it's not a big deal, but what if you had 50? then your block page iwll be ten feet tall!)
if you want more explanation of how i solved this, let me know and i'll do the walkthrough for the 'simple approach' i'm using as it works perfectly...
#4
This is by design.
We used to have it the way you describe above, but that was changed to the current (not-limited-to-freetags) implementation by popular demand.