I cannot print my terms CCK Taxonomy SSU when I use print $terms?! Why is that? It's the same for the released and dev version.

All my other terms print just fine when I use taxonomy select lists, autocomplete etc.

Comments

rconstantine’s picture

rconstantine commented

I suspect it is because $terms is probably a $node sub-variable. Is it used in theming? That's my guess. The design of this module was specifically to avoid using this taxonomy field as a tag to a node. I didn't want this field searchable through the regular means which helps prevent its discovery and display through regular means as well. To do this, the terms are kept in their own cck table (as well as taxonomy tables) but not placed in the node_term table. SO... if $terms only grabs things from the node_terms table, it won't grab these terms. That is by design.

With that said, there is a feature request already in the queue, if I recall, to optionally include the data into the node-terms field. I don't know when I'll have time to get to it.

storbaek’s picture

storbaek commented

Thanks for the clarification. Your explanaion makes sense, but of course restrict me from using the module. I've tested all other similar modules and this is the only module that provides the intuitiveness and simplicity to browse and select many terms I prefer.

As the taxonomy is one of Drupals true core strengts, I hope we will see this module added with the functionality of showing the terms as tags on a node. Simply in a way that allows the users to select any number of terms, which then will be shown on the node. I see that other modules seem to show the whole term breadcrump (the whole path of terms and sub-terms), and not only the term being chosen being another point of attention to consider.

rconstantine’s picture

rconstantine commented
Status: Active » Closed (works as designed)
rconstantine’s picture

rconstantine commented
Status: Closed (works as designed) » Closed (fixed)
rconstantine’s picture

rconstantine commented
Status: Closed (fixed) » Closed (works as designed)
rconstantine’s picture

rconstantine commented
Status: Closed (works as designed) » Closed (fixed)

What am I doing? I did mean to close this!

storbaek’s picture

storbaek commented

Hi Ryan

I am stilling looking for a module similar to yours that enable me to print the tabs on a page that was selected by a user on a input form. I noticed that this module was updated, but I was not able to see what was changed. As this case changed status to closed, I wonder if this functionality has been added?

Thanks for otherwise great module
Dan

storbaek’s picture

storbaek commented

Hi Ryan

I am stilling looking for a module similar to yours that enable me to print the terms on a page that was selected by a user on a input form. I noticed that this module was updated, but I was not able to see what was changed. As this case changed status to closed, I wonder if this functionality has been added?

Thanks for otherwise great module
Dan

storbaek’s picture

storbaek commented
Category: support » feature
Status: Closed (fixed) » Active

Could be great if we could print the terms using taxnomy_ssu, which does not seem to be the case this.

rconstantine’s picture

rconstantine commented

I need to do a better job of my commit notes. Anyway, there's a new checkbox when you add SSU to a content type. I think it says something like "Add terms as node tags" or something. See this: http://drupal.org/node/159950

By doing so, your $terms thingy might work now.

If not, notice I was flip flopping between closing this issue and marking it as 'by design'. In other words, if this doesn't do it, I'm not sure I'll even try. But patches are always welcome.

storbaek’s picture

storbaek commented

Thanks Ryan. I've just tested the field and it works like a charm printing the terms. We use it site-wise and together with your multiple-term selection options, it now works great.

I've meant to ask you under what circumstances or use cases would you be interessted not to show the terms on an input form, but only be able to choose between them on the input form?

Secondly, there is also a a term rating functinoality included and I was interessted to know what usage this could have?

rconstantine’s picture

rconstantine commented
Status: Active » Fixed
rconstantine’s picture

rconstantine commented

Sorry. I meant to answer your questions.

First, I thought I had a README for this project. Seems I still need to make one. Anyway, the reason I need 'hidden' terms (which of course are still visible when you edit the content) is for other modules to cull that data and use it and in my case, I don't want these terms clicked on and all nodes with that term listed or exposed. In fact the content types are nodeprofiles, so they have personal user data on them. My new handshake module is how I expose user data. I have other upcoming modules that will use the CCKTSSU data as I've described.

As for the ratings, there are any number of ways you could use this. I suppose it is primarily useful if you have the CCKTSSU fields in nodeprofiles so you can find out something about each user. But you could have a taxonomy about hobbies or interests and users could rate how interested they are. Or they could rate their skill level. Or with another taxonomy, say movie titles, you could list ratings. Or you could have a taxonomy of classes and instead of ratings, you could list time slots to assign to each class (althoug that would probably be better done another way).

I hope that makes sense. You may never need that feature, just as nobody will probably ever need the 'known address list' feature in my cck_address module.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)