Closed (won't fix)
Project:
Term Fields
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Jul 2009 at 00:51 UTC
Updated:
9 May 2011 at 03:06 UTC
I've just hacked the 6.x-1.5 release to add a node reference field, and this is the patch against head (manually copied into new code - no testing!)
I don't need views integration / term displays, so it does need some work, but hopefully serves as a starting point for someone.
| Comment | File | Size | Author |
|---|---|---|---|
| term_fields.module.nodereference.diff | 1.98 KB | alan d. |
Comments
Comment #1
b-prod commentedI don't think this is the purpose of the term fields module. If you have to store relationship between nodes and taxonomy, there already are the following modules:
If you think this feature is really necessary, please reopen the issue and give me more information about your needs and why the modules above do not feat your requirements.
Comment #2
alan d. commentedFair reason. Rather than having too many modules enabled, a complex site has enough modules to avoid loading another one when a simple hack will do :) Anyway come D7, this will not be an issue every again!
Comment #3
alan d. commentedGuessing you have no interest in a user reference either? Will submit the patch if your interested, but that is another TF field that needs to be ported to D7 fields ...
Comment #4
b-prod commentedThanks for beeing involved in this project!
But for userrefrerence I think it is the same thing than for nodereference field: not really the purpose of term fields module and probably handled by one of the module listed above.
And as you said: soon will arrive D7 which will fix all of that ;)
Comment #5
zazinteractive commentedI would like to attach nodes to my terms so I can display a field from each node on the term pages. The above modules can't handle that.