Showing tag cloud with various font sizes when viewing tags attached to the current node
martinjbaker - September 3, 2009 - 16:40
| Project: | Views Tagadelic |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I have a view which takes the current nid and shows a block with its tags. This is then being used in a panel page.
The problem I'm having is that all the font sizes are the same. In a way this makes sense since on the current node the count for each tag is "1", but it doesn't look much like a tag cloud! Is there any way for Tagadelic Views to use the total count for each tag so they are sized differently or do I need to dabble with the API?
thanks
Martin

#1
Same problem here, which arguments do I have to add to show the different weight of the tag?
#2
Is it not possible to create a cloud-view for a single node? The cloud view works fine until i add the nid-argument. Then the view shows only the terms, but not in different sizes.
#3
Not an expert in this module, but is it possible that it's filtering on the node id... so that it's just showing tag weight for this node, and since this node only has each tag once there are no weights.
It would seem the node is an argument for the view, so seems a likely case.
If that's the case then I'm not sure if you can have a global weight to the tag, but a filtered subset just for the node.
#4
But why is the tag weight ignored, when i add the nid as an argument? I wanted to add the term weight as an argument, but I can't choose the term weight as argument.
#5
Umm... you can't add term weight as an argument. Term weight (how many times it's been used) is something computed by views_tagadelic.
The nid is the argument that limits the terms to just those used on the node. Since each of those terms is just used once for this node they all have the same weight for this node.
#6
So which argument or workaround can i use to limit the cloud for the viewd node. Somehow this has to work, because the custom form does exactly that.