Closed (works as designed)
Project:
Tagadelic
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Dec 2006 at 03:53 UTC
Updated:
7 Dec 2007 at 12:32 UTC
The function tagadelic_tags_lists($node)
will only show lists of freetagging vocabularies terms, but not of other vocabularies.
I'd like it to show terms of other vocabularies as well.
Is this not a problem of tagedelic but of taxonomy_get_vocabulary($vid);?
Comments
Comment #1
Bèr Kessels commentedI amsorry, but I cannot confirm this. The code is clear too:
Or, in human language: Iterate over all the vocabularies!
Comment #2
Stephan_M commentedThank you for taking a look.
Only if i enable "free tagging" for the vocabularies they will show up in the tagadelic block. Do you have an idea what might cause this behaviour?
Comment #3
kpaul commentedi'm seeing this too... any ideas?
Comment #4
Bèr Kessels commentedPLease give me the versions you are using.
Comment #5
Stephan_M commentedSorry - i missed this thread, because i went for another solution. I am fine with it only showing free-tagging vocabs.
Still the version i am using is: tagadelic.module,v 1.35 2006/11/02 13:04:38
Comment #6
bohtho commentedSame for me as in 4.7-issue about this. Version 5.x-1.x-dev
Comment #7
doc2@drupalfr.org commentedHi, I have the same problem on Drupal 5.1 with tagadelic.module,v 1.36.2.3 2007/03/13 09:58:31 ber Exp $
I think we can consider that as a bug.
Yet I cannot just switch to freetagging as, for a Tagadelic-independent reason, my freetag enabled vocabs disappear from the editing form (by the way, from both the Category and CCK Taxonomy field fieldsets). But mainly because I do NOT want freetagging on my vocabs.
As this "Tagadelic list on a block" feature is a fantastic workaround for newbies for displaying the Terms almost somewhere else than on the nodes content's bottom (*), I think this should be solved. I badly need it! In plus of showing the Vocabularies' label, it provides their breadcrumb link! These already are two great improvements in Taxonomy!!
(*) I removed the body bottom's links and terms by removing --warning: newbie method here--, in the node.tpl.php file (from Drupal's active Theme), the content of the "print_terms" div, including them.
I tried to create a block with PHP-code entry format enabled, containing the previously removed pieces of code, but it wouldn't work. (I know, it's quite a barbarian way to 'develop' ; )
Thanks for this great module anyways! Any (patch) suggestion?
Comment #8
doc2@drupalfr.org commentedYou may bookmark this http://drupal.org/node/48261#comment-252441 to follow any answer there.
Comment #9
lennart commentedThis still seems to be true. All freetagging vocabularies will be shown in the block, but not others
Comment #10
lennart commentedAs soon as I change one of my "non-free tagging" vocabs to a "free tagging" vocab it shows up in the block just fine. When I change it back it once again disappears from the "tags for ******" block.
Comment #11
sdecabooter commentedI think some people in this thread are talking about other blocks.
However, i notice the same behaviour as the starter of this topic.
When you enable the 'tags for the current post' (so not the 'tags in @voc' !), as mentioned in the first post of the thread, it does indeed only show tags from freetagging vocabularies. This is because in the function
tagadelic_tags_lists($node)you have the following on line 191:foreach($node->tags as $vid => $terms) {The
$node->tagsarray only contains tags (thus terms from freetagging vocabularies). If you would want to show terms from all vocabularies, you could find them in the$node->taxonomyarray. However you wouldn't really need the tagadelic module to show all terms related to a post... This can be done with an easy php snippet in block.lennart: are you also talking about the 'tags for the current post' block, or about the 'tags in ' block? Because those are two different things.
The last one should work with non-freetagging vocabularies too (i just checked it), the first one does not.
Comment #12
sdecabooter commentedHmm i messed around with the code blocks :)
Hope the comment is readable nonetheless.
Comment #13
lennart commentedsvendecabooter
Thanks for the tip. I was talking about the 'tags for the current post' block.
Comment #14
Bèr Kessels commentedThis is by design.
However, I am thinking of removing these blocks entirely, they belong in another module IMO.