Your module is very much what I need. Thank you. I am not sure wether my requests are about support of a feature that I don't manage to handle or if I ask for new feature. In the last case, I think this would be very useful:
1- Autopopulating fields with the terms hold by the nodes - Feature request?
As long as I understand it, the created fields already includes the terms of the chosen vocabulary (to the contrary of Taxonomy Fields, right?). But, currently, once defined a field, we have to "repopulate" each node backend with the terms of the same vocabulary, although the node already holds them. This makes a redundancy and opens a breach for possible confusion. Indeed, for a specific vocabulary of a given node (a defined field), one term could be chosen as taxonomy term ("crosslink") and another term could be chosen as a field value. This could lead to choosing and displaying inappropriate terms.
Would it be possible to set, as an option, to aotupopulate the field values with the terms hold by the nodes, that is to say the possibility that the selected terms of a given node become the default values of the (vocabulary) corresponding created field?
2 - This feature (?) brings up an issue: a node would display twice the terms.
I would still like to display the terms as field values. However, I would like to display them as if they were still terms, that is as "cross links". As a result, I would get twice my tags. Once in the fields, and another time with the default node view at the bottom of the page (thing that I don't know yet how to hide, contemplate doesn't seem to allow such handlings).
3 - Feature request ? Could it possible to assign more than one vocabulary to a single field (as Taxonomy Fields would allow, right?)? You would offer checkboxes in the "Widget settings" fieldset, instead of radioboxes.
In the end, a huge thanks because your module appears light and easy! I really wish these features would be wanted and useful enough for you to implement them, considering your possibilities!
Regards, Arsène
"Equivalent" post for Taxonomy fields: http://drupal.org/node/156479
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Image 2.png | 116.55 KB | doc2@drupalfr.org |
Comments
Comment #1
robertdouglass commentedWhat I had in mind for this module was that you would probably *not* have the taxonomy form on the same content type that you use the field form. In fact, I went to the trouble of making the content type checkboxes on the vocabulary form optional instead of required so that you can have vocabularies with no content types. I don't really see the benefit in having the cck field populated with the values that you chose in the taxonomy field. I also don't have any interest in making this module persist its data to both the cck field table and to the term_node table... this just seems messy and wasteful to me.
As for combining vocabularies into one field... could you provide me with a compelling use case where you would need to do that?
Comment #2
doc2@drupalfr.org commented-
That's a main, useful, feature. But yet, the terms displayed appear as text and loose all the benefits of the hypertext "crosslink" feature.
Now, as I can't give up the terms' crosslink essential feature, I could not use the option of disabling my vocabularies from my content types, and just use the CCK Taxonomy fields instead without link feature. That's why I was thinking of autoselecting the node terms in the CCK Taxonomy fields (rather than autopopulating, which your module already does). But this no longer a feature request to me. If...
As a result, the new feature request would be to have the CCK Taxonomy fields' values displayed as terms, that is to say as links. Do you think it's a valuable feature?
- As for having several vocabularies for one field, it would allow to unify the display of existing vocabularies while keeping them separated for the ease of navigation (with Taxonomy_DHTML).
Ex.: Managing document, we have quite a lot of metadata. We could have, for example, a unique "event" field containing the terms from different vocabularies, such as:
- for a picture, the title of a theatre piece OR of dance show
- for a single movie presenting different events, the titles of all the theatre pieces AND dance shows or other vocabularies, not specifically artistic or related.
Comment #3
doc2@drupalfr.org commentedHow much would you ask for to develop such features? Each? Both?
Comment #4
robertdouglass commentedI still don't buy into the concept behind either of these feature requests.
If you need the crosslinking feature of taxonomy, you should be using taxonomy in its traditional sense, not this module. What I *would* like to add is a formatter that links to a view and passes the term id into the view as an argument. Then you could simulate the crosslinking you're talking about and much more. I'm not quite sure how to go about doing this at the moment, and place higher priority on the sort and freetagging features I've mentioned in other posts.
As for combining lists into one... I don't like this. There is no difference between that and having two select elements on the same page... except that two select elements is clearer and semantically more correct. I'd encourage you to rethink the data models you're trying to express.
Comment #5
doc2@drupalfr.org commentedOkay. I'll just keep to the main one for now: the CCK Taxonomy field values as terms. It's just a workaround, because I'm a PHP newbie (like many other drupalers), for having the tags displayed in the node div
from the node.tpl.php file (drupal > themes), instead of having them displayed in the node div
which shows them at the bottom of the node display.
My problem is that I don't know how to easily display my terms (vocabularies) within the node content.
CCK Taxonomy fields brought to me the idea of a potential great solution by displaying the terms as field values (fields) because there are many displaying options with fields, such displaying label or not, inline or above, in the teaser or full view, etc... but without the crosslink feature.
As I need those links, I need to enter my metadata twice, with the risk of entering different data in fields and toxonomy, and I get the terms displayed twice.
What I understand now is that the crosslink feature relies on taxonomy, and therefore I cannot give up its use. That shifts me back to the great advantage of an eventual "autoselect" node terms feature, so that they would not have to be chosen twice in an edit form.
I know this is very specific to my use, but I hope that other users need such features as well. If you do, please sign in and let us know here.
I've tried some tricks such as displaying the node terms in a block:
- doesn't work with tagadelic http://drupal.org/node/104891
- don't know how to do with this snippet http://drupal.org/node/48261 (cf. my post) to get only the node terms instead of the whole site's.
- I tried to cut/paste the second piece of code into a PHP enabled block... It does not work.
I'm not sure what else to try. I just know that I still need to use the taxonomy features, while I'd prefer not having them displayed twice.
Now, have a look at the following page (screenshot link up there). Every field you see is a CCK taxonomy field. You'll notice that I've disabled the display of the terms before the so-called "links" (Click to bookmark, etc.) You imagine that having them displayed there, in-between the attached files and the "links", is not very convenient, especially if the file holds much more metadata than this screenshot, and if you need to scroll to reach them. You'll probably agree that having them just in the fields would be much better than having them displayed twice.
What you could notice as well is, in the right column, my try to display the node terms in a block. But admit that it is a waste of space to have them displayed here and there... and that having the node terms as links in the fields would be the most convenient display.
Comment #6
doc2@drupalfr.org commentedFirst hints for an alternative: http://drupal.org/node/158509 But this is no more about autopopulating/autoselecting node terms...
Comment #7
doc2@drupalfr.org commentedSorry for the previous long and messy posts. I was a n00B!
I found the module http://drupal.org/project/term_display to enable "weighting" the taxonomy terms, while still not quite perfect (fixed theme).
About the redirection feature, some other requests:
Here: #165878: Keeping link to taxonomy/term/xx when displaying a CCK Taxonomy Field
And there: #185955: Allow showing terms as links in Views