Relationship between tag size and the number of nodes using it.
nbz - August 8, 2008 - 19:28
| Project: | Tagadelic |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Is there a relationship, or is it just random?
I expected a simple correlation between tag sizez and the number of nodes using them, but that does not seem to be the case.
Looking here: http://www.therevival.co.uk/tagadelic/chunk/4
"q and a" is tiny, same size as culture, the the former has 32 nodes using it, the latter just 2.
#1
fwiw, on the above link, I cleared the cache via phpmyadmin, uninstalled the module, removed the variables in the variable table, re installed the module, increased the levels to 16, the terms to 80 and put term ordering on random.
I would suspect that that would get rid of any cruft that could have potentially affected the tag size (and the setting the order to random is also not the issue, I had a look before that and it still was a off in a similar way, just the terms in alphabetical order.)
#2
I have the same issue. I've cleared the cache. I'm using the latest dev as of this posting.
#3
I cannot see the problem. Can this either get a more detailed description, or be closed?
#4
As an example. if you have a look at the link in the first post you will notice "Direct Debit" is large letters and lifestyle in small letters.
"Direct Debit" has 0 (zero) posts using it while "lifestyle" has 37. The tag sizes seem to have no correlation to the number of nodes with that term.
#5
Are you using unpublished nodes and/or some access module? If so, 141682: access control aware tag clouds is probably the answer.
#6
I am using ACL and forum_access, but only for the forums, which that page does not correspond to.
None of the terms on that page use access control. In other words, I do not use that taxonomy on nodes which are in the forums.
(Besides, if I read that issue correctly, I assume that the issue will only be for people who are limited by a form of access control - my user account can see all content.)
#7
tagadelic does not (yet) take sql-rewrites into consideration.
It will therefor calculate the clouds based on ALL nodes, regardless of their visibility, access and so forth.
So, if, for example, you have thousand nodes invisble for your users, because of some access system, but only 50 visible, the cloud will still show as if all 1050 are visible.
Bèr
#8
On the mentioned site, none of those tags are used for "invisible" nodes. Those tags are only used for nodes that are not "access controlled".
The actual mapping of size is wrong.
#9
Probably a CSS-issue then.
#10
no answer. closing.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.