Well, i think i'm misunderstanding this module's goals since i was expecting to have two main features using it, a user's personal tag cloud and one for the single node with all the given tags for that node.

I've already asked about the first one and that's not provided by this module but then i thought it should have been easy to show a community tag cloud for the single node.
It was, indeed, but then i realized that it was not only a tag cloud, but the complete form to add tags so that the anonymous user or simply whoever lacking the tagging permission would not have seen even the contained tag cloud.

I must say this isn't what i was expecting but the real issue is that i don't get the point in this behaviour:
tags are a semantic way to browse a website's content, they are a different way offered to a visitor to find contents basing on a personal interest, why should we prevent them to use such a feature just because we decided not to grant them the permission to add and edit that tags?

I've tried to figure out a different way to manage this, but i wasn't unable to find a good one since i've worked with views and it seems we can't use the tagadelic views module or simply count the terms recurrence in order to generate a tag cloud starting from a views query, the same reason why we can't have a tag cloud for the single user's tags.

i know i could simply print the normal tags array but that's the deafult drupal behaviour so i wouldn't be really using the powerful user's relationship of the community tags leading us to have weighted tags basing on counting how many user's tagged a content in the same way.

I have to say that this deadly reduces my chance to use this module usefully but i could be wrong, i could be missing something so that's why i'm writing this,
is there any way to print a community tag cloud inside a node regardless of permissions about adding or editing the community tags vocabulary terms?
Thanks,
Da.

Comments

valderama’s picture

valderama commented

true!

when using the tagadelic tag-cloud the size does not on how many users have used this tag.

+1 for this feature (tag-cloud for each node - also visible for anonymous users)

entrigan’s picture

entrigan commented

These are some key issues you get at. Right now the module supports on a very specific use case.... and unfortunately it is becoming outdated very quickly. What we need is 1) Remove Tagadelic Dependence 2) Expand API and 3) Expand configuration options.

Will get to these as time permits, will also test and accept patches towards this end, and of course we are still looking for another co-mantainer :)

entrigan’s picture

entrigan commented
Version: 6.x-1.0-beta2 » 6.x-1.x-dev
chaps2’s picture

chaps2 commented
Version: 6.x-1.x-dev » 6.x-2.x-dev

@planctus - some good points, and you highlight some inconsistent and/or illogical behaviour that's been bugging me too. BTW - anonymous or permission lacking users could see the tag cloud - but only when it was inline ;)

Have just committed changes which:

  1. Add "view tags" permission - designed for anonymous users to be able to see the tag cloud and nothing else. Users with "tag content" permission don't need to have "view tags" as well.
  2. Changed behaviour so that if user has "view tags" then they see the tag cloud on all inline, tab, and block tag displays.
  3. I've disabled anonymous tagging completely. It doesn't work so should never have been allowed. Out of "edit own tags", "tag content", and "view tags", only the latter is valid and effective for anonymous users.

Notes:

  1. The validity of the "login or register to tag" message shown to anonymous users is dependent on site configuration. i.e. authenticated users may not have "tag content" permission. Need to check what comment module does.
  2. The display for users who have tagged but do not have "edit own tags" permission needs work... but there are quite a few outstanding feature requests that deal with display themeing etc.
chaps2’s picture

chaps2 commented
Status: Active » Fixed

I've just added argument handlers to community tags aggregate views which permit "most popular tags for the node" type views. See #90434: Add counting fields to views integration.

If you expect heavy tagging activity you could use Views Cloud to create a cloud block of the top n tags with a more link to a page with a pageable/sortable table of tags for the node. In this case I would not give anonymous users "view tags" permission.

@planctus - I think your original requirements can be met now (even if you no longer need it) so I'll mark as fixed.

planctus’s picture

planctus commented

Thank you, i don't need that at the moment, as you said, but i will certainly use this module's feature in some projects to come :)
Da.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.