First, thanks for another great module for which I see a lot of use cases.
The project page describes what kind of clouds can be generated with this style plug-in, but not how to do that. After playing with this style plug-in for a few minutes, I couldn't figure out how to get something to show up in the "cloud weight field" field of the style plug-in settings. (I didn't need it that bad, but that's already more than most people would try).
So far it's more a support request than a feature request, but I think that the best way to explain how to set things up is to have a default view. Maybe a simple tag cloud would be the best example, with a list of taxonomy terms weighted by the node count for each term.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | views_default_views.patch | 11.54 KB | quicksketch |
| #2 | views_cloud.txt | 3.41 KB | designerbrent |
Comments
Comment #1
jeff h commentedI really agree - a default view would be great. I tried hard to replicate the example given by the picture on this module's page (http://drupal.org/node/309754) but without success. How did you get the number of articles by each author? Was the view a Node-type view or a User-type view? Did you have to use custom PHP, or arguments, or how?
Please share your secrets :)
To answer the first part of this issue, regarding missing "Cloud weight field", I think a lot of people aren't getting what this is for. Would you consider the following?
* add an inactive item to the empty dropdown to say something like "View has no numeric fields"
* change the help wording from "This field will be used to control the size of each row in the cloud." to "This field will be used to determine the weight of each item in the cloud. Your view must contain at least one numeric field."
Jeff
Comment #2
designerbrent commentedAfter alot of poking and reading of the code, I finally figured out how to create a tag cloud. The trick is adding an argument. Without that, I won't work.
While it's not in the form of a default view, I have created a sample view and exported it. You can import it by going to admin/build/views/import and pasting the contents of the attached file into the window. As configured, this creates a tag cloud of all the taxonomy terms.
Hope this helps get a few people closer to having working clouds!
Comment #3
StevenWill commenteddesignerbrent: thanks for the view export, A great help with using this module!
Comment #4
StevenWill commentedI just wanted to point out that you do not need to have a argument, but you do need to have the "numeric" field as the FIRST field. Removing the argument in the exported view above will send the user to the tag node listing when clicking a tag in the cloud.
Comment #5
szy commentedThanks, as it's not obvious to define term argument to have view working.
Have you got working 'tagadelic style' sorting properly?
Szy.
Comment #6
cybershan commentedthank for the great plug-in.
just one question, how can I change the link to terms link directly "term/termid" instead of link to "/cloud/termname"?
thanks in advance.
Comment #7
sharrison commentedAt the start of this thread, Jeff wrote, "I tried hard to replicate the example given by the picture on this module's page (http://drupal.org/node/309754) but without success."
Right now, I'm in the same place.
I'm making plenty of user clouds but none that display a list of single user names weighted by their total number of posts.
How did you do it, designerbrent?
Thanks,
Stan
Comment #8
hujia commentedHello all,
I imported the views_cloud example, and also followed the step by step instructions, and there have been a couple of taxonomies in the site: but the output is always blank under the title of Tag. What can go wrong? thanks! huj
Comment #9
quicksketchhujia: You have to make a Page display for your terms to actually link to.
I've added the following patch that makes 2 default (but disabled) views.
- cloud_tags: A common tag cloud.
- cloud_user_posts: A cloud of user names, weighted by the number of posts each user has made.
Why are they disabled by default? Because it's not entirely expected that enabling a tag cloud is going to override the default taxonomy/term page, or that a cloud of user names is going to create a tab on user profile pages. Since these views may cause unexpected behavior, I've left them disabled by default, but added a note to the README file, saying you can use them as templates if desired.
Comment #10
quicksketchComment #11
szy commented@qs,
Could you please tell us, how can I:
1. display a cloud with the most popular 20 tags?
Now limiting by number in options is sorted alphabetically,
not by popularity.
2. display a cloud of tags for a NID argument from URL?
Looks simple, but... it is impossible now. I still get red
'no available numeric fields' warning...
Thx,
Szy.
Comment #12
quicksketchSzy: Views Cloud now comes with a view that is a tag cloud. It's also documented in the README.txt file. To limit it to 20, just put a limit of 20 items on your view. To get the 20 most popular... I'm not real sure. I think you'd need to use the recommended Taxonomy Node Count module in order to get that sort (it'd be more efficient too).
For your second one, you'll need to add TWO arguments. The first for NID and the second for what you want the cloud to be based on (such as Taxonomy: All terms). Again, refer to the readme and sample views.
Comment #13
szy commentedThere is no option to sort by tag count (popularity)
for node view with Term Node Count module.
With two arguments for second view, tag cloud is not
a cloud actually, because tags do not get its proper
(different) size. It looks like a unformatted list.
Maybe anyone else knows any tricks for these views?
Without them, View Cloud for nodes doesn't differ much
from Tagadelic, I think.
Szy.
Comment #14
quicksketchThis is because the CSS is not loaded on the Views configuration form (since it's pulled in via AJAX). Save the view and then look at it on a page or in a block, where the CSS will be loaded.
Comment #15
szy commented:), I have checked it on my webpage off course.
They get the same weight in the cloud, because - when
argumenting by NID - every tag has the same number
of occurances: 1. Only in this node.
So they lose their weight from all the nodes they belong.
Szy.
Comment #16
quicksketchAh right. In that case what you are trying to do is not currently possible, because there is no way to create a relationship based on a node's current terms. However this isn't something that Views Cloud would provide, it's a lack of adequate relationships you need being provided by Views or other modules.