Hello,
I am install you module and try implement them on my website. I am add new block called "tags for the current post" - It in order show name all terms and vocabularies, but I see them like menu (

  • ) - so, is there chance to customize module to see tag cloud for block "tags for the current post"?
    Next problem is that I see names of vocabularies... So, I want see only names of terms... Now I will see some tags twice - one for vocabulary and one for term. So, please help me... You are my last chance...
CommentFileSizeAuthor
prtscr.PNG10.56 KBrodman69

Comments

rc2020’s picture

rc2020 commented

Hello,

I too am looking for an answer to this question. I try to add the NID as argument and add a php snippet:

if (!$args[0]) {
$args[0] = arg(1);
}
return $args;

under handling code, having tags show up as a block.

But I get an SQL error about the implode function.

If anyone has figured out an answer to this it would be great to know it!

zilla’s picture

zilla commented

getting the same issue - the auto-generated Blocks for each content type's tags are in fact FIRST pulling the defined taxonomies before the 'free form' tags and in turn generates a cloud box that is simply the main categories again, not the terms...going to post a separate issue for this request block code...

rc2020’s picture

rc2020 commented

Actually I was thinking about this and I realized that tagadellic does weighted tag clouds. So the more times a term has been tagged as that, the bigger the font size is on the cloud. We want this for current posts, right?

But if the current post has all the items tagged just once, the tag cloud wouldn't weight them at all, as thats how the module is built.

Maybe if it looked at the entire taxonomy scheme, took the terms from the current post, and weighted them according to their weight in the total taxonomy scheme?

But I don't know how to go about this.

Bèr Kessels’s picture

Bèr Kessels commented
Status: Active » Fixed

please create a proper feature request for this issue.

Status: Fixed » Closed (fixed)

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