Autopopulating Taxonomy fields with the terms hold by the nodes
| Project: | Taxonomy Fields |
| Version: | 5.x-1.4-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi,
I try to use your module, which seems very useful, but yet still a bit complex to me. Anyways, it could fit many of my needs actually. Not sure wether I ask for support or feature request...
1- I think you already answered many of my current "features request" in the dev module you released here: http://drupal.org/node/151484 . But when will they be officially implemented? I wish I could test it, but with not much time I cannot take the risk to install a "too dev" module at the moment on the site I dev.
2- Could you as well implement a function, as an option, that would autopopulate the fields of our choice with the terms that the nodes already hold. I couldn't figure out wether it is possible or not. Could you tell me how, please?
3- Could those field values be kept as "crosslink" tags? It could be implemented as a supplementary option.
4- and, thus, could those field values replace the default display of the terms at the bottom of the page?
Thank you very much for your contribs.
Arsène
#1
CCK Taxonomy fields equivalent at http://drupal.org/node/156494
#2
Hi,
in regards of the version on http://drupal.org/node/151484 I can't tell when it will be stable and implemented. I just droppped it there yesterday to be checked while developing and implementing other features. There is still quite a lot to do...
I can't really help you with the other requests as they are functions of the field modules, especially the cck taxonomy fields module. Please note that this module is very different to mine. I just use field modules to assign fields to taxonomy terms, I don't create new fields.
#3
Thanks for your quick answer. I've just realised that your patch was so recent. I whish it would be implemented soon! Good luck and bon courage!
I understand better your module now. Effectively, the fact that it does not populate the fields with vocabularies does not fit my main needs. It could rather trigger fields according to the terms, which is its main purpose and my be helpful. Cf.:
You ARE able to create new fields anyway, thanks to your module, as if you were adding a field to a content type: you can still either "Add existing field" or "Create new field". Or do I miss the point with:
Do you mean, you don't create "autopopulated" fields? Anyway, nevermind this last remark.
Thank you sincerely.
#4
yes you can create new fields, but no new field types.
sorry for confusion.
#5