Page 1 of 1

Tagcloud parameters

PostPosted: Sun Jul 24, 2011 3:09 am
by Marza
The tag 'tagcloud' has four possible parameters: amount, minsize, maxsize and underscore. The first three can be set in the configuration, and when [[ tagcloud ]] is used in the sidebar, these settings are used. It makes sense that the page on which the full tag cloud is displayed, doesn't use the same settings, as it allows for a bigger font size and it is meant to display all tags.

Being able to set different parameters for the full tag cloud would be nice, but isn't urgent. It would make sense though, if at least the underscore parameter would be added to the configuration and if it would be applied to the sidebar as well as the full cloud. At the moment their doesn't seem to be a way to make them look the same. Or did I miss a possibility to add the parameter to the settings of the extra page?

To see what I mean exactly, please visit amsterdamcentraal.nl, open the tab 'Trefwoorden' in the sidebar and click (alle). In the sidebar you'll find tags separated by single spaces, whereas the full tag cloud still uses underscores.

On a side note: it is a bit confusing for users that they can separate tags by underscores, even though the entry editing page doesn't mention this option. At least in Dutch it says: "Tags scheiden met een spatie. Bijvoorbeeld: films jedi starwars (niet 'star wars')" (Separate tags with single spaces. For instance: movies jedi starwars (not 'star wars'). It would be nice if this could be changed in a future PivotX edition.

Re: Tagcloud parameters

PostPosted: Mon Jul 25, 2011 8:51 pm
by hansfn
Hi, Marza. I see the problem, we might fix it, but there is a work-around:

1) Create a page called for example Tag Cloud, that contains a tagcloud tag with the settings you want. (Set amount so high that all tags are included.)
2) Change the .htaccess file so the URL tags is an Alias for that page (instead of a RewriteRule).

Re: Tagcloud parameters

PostPosted: Mon Jul 25, 2011 9:22 pm
by Marza
Hi Hans,

Thanks, the work-around will do for now. Perhaps updating the info could get priority over a fix, as not everyone even knows underscores are allowed and can be changed into single spaces.