Are there any plans to port this module to D6? I'm currently making a half hearted attempt to do this myself, but I'm stuck, as I don't know the API at all.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | fieldreference-6.x-hax.tar_.gz | 10.39 KB | cafuego |
Are there any plans to port this module to D6? I'm currently making a half hearted attempt to do this myself, but I'm stuck, as I don't know the API at all.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | fieldreference-6.x-hax.tar_.gz | 10.39 KB | cafuego |
Comments
Comment #1
deekayen commentedI don't have any near-term plans to do it on my own, but I'll commit a patch if you do the work.
Comment #2
cafuego commentedWell, I can get it to the point where it allows a field to be chosen when creating the new content type, but I don't know anywhere near enough about module development to get it to display its input fields with values when adding new content. I'd probably need to spend 2 weeks just looking at the API.
I've worked around it for now by hacking node.tpl.php to display itself differently depending on the node type that is displayed and using nodereference. It's ugly, but it works.
Comment #3
guardian commentedi'll try to have a look at it, but this is not something high on my list
Comment #4
cafuego commentedI've packed up and attached what I've done sofar. I doubt it'll be highly useful, but still... prolly won't hurt.
Comment #5
danielb commentedDid you upgrade the existing module to be compatible with D6? Personally I would write it from scratch and sap all the awesome features from D6 nodereference - that's what I did with some of the modules I maintain.
http://drupal.org/project/blockreference
http://drupal.org/project/viewreference
also I upgraded this module from D5 to D6 by basically writing it from scratch on top of nodereference - was fairly easy
http://drupal.org/project/revisionreference
I would be willing to help but I've so many modules that are finished i could be polishing up and releasing when I'm not playing tf2 :/
Comment #6
guardian commentedyeah i lack time lately
i'll give it a first shot in the next days
Comment #7
libeco commentedsubscribe
Comment #8
a_c_m commentedsubscribe
Comment #9
break9 commentedI would like to see this for 6 also. I am not sure how to code it correctly or I would do it myself.
Comment #10
ultimateboy commentedSubscribe. Would love to see this for 6.
Comment #11
panchoI need this for an upcoming project. So I might take a look at what needs to be done.
danielb pointed us to a good direction: Not only that we should reuse nodereference's code, it might even make sense to build this on top of nodereference. Some day it could be rolled into nodereference's project.
Comment #12
guardian commentedWell I used nodereference as a reference when implementing fieldreference. I'm not sure much code can be reused though.
Comment #13
tyromind commentedWhat's the current status?
Comment #14
Ylan commentedSubscribe, this would be quite usefull.
Comment #15
Rosamunda commentedDoes #4 works?
Comment #16
Rosamunda commentedComment #17
momper commentedsubscribe - a working 6 ver would be woderful ...
Comment #18
Tenx-1 commentedSuscribing , defo need this
Comment #19
deekayen commentedComment #20
deekayen commentedoptgroups don't appear to be supported for selects in 6.x
#306930: Support optgroups in allowed values
Comment #21
deekayen commentedActually, I think what I need for my case is to reference the field_name and type_name from content_node_field_instance, not the data in a field from a node.
Comment #22
gunzip commentedsubscribe
Comment #23
scalp commentedsubscribe. any idea if this is going to happen?
Comment #24
talatnat commented+1, subscribing
Comment #25
Leonth commented+1 subscribing
Comment #26
Flying Drupalist commentedsubscribe
Comment #27
tpainton commentedThis is a must. Subscribing.
Comment #28
sbydrupal commented+1 Thanks
Comment #29
felipe commentedsubscribing
Comment #30
Parkes Design commentedsubscribing....
Comment #31
bcarlson33 commentedsubscribing
Comment #32
paganwinter commentedSubscribing...
Comment #33
appel commentedAnother subscriber.
Comment #34
ycwjjjj commentedSubscribing
Comment #35
khan2ims commentedOne more!
Comment #36
translector commentedsubscribing
Comment #37
carwin commentedsubscribing
Comment #38
NathanM commentedSubscribing, but there doesn't seem to be much going on here.
Comment #39
ram327 commentedSubscribing. I would love to see this happen.
Comment #40
willhowlett commentedsubscribing
Comment #41
ggevalt commentedNot subscribing as much as wishing that someone would have the time and knowledge to port field_reference to D6. This would be of incredible use to us. Here's to hoping.
Comment #42
sumaiyajaved commentedsubscribing
Comment #43
arski commentedsub :(
Comment #44
maulwuff commentedsub
maybe this module will work for some of the subscribers, too:
http://drupal.org/project/nodereference_field
Comment #45
jvdurme commentedMmm, and how would that work to reference a field's content? Can't seem to get it.
Comment #46
nlambert commentedThere is another solution.
Use cck node reference and then create a view. Here's how :
http://drupal.org/node/289738
Comment #47
danielb commented^ That's pretty clever, you could also do a view reference
Comment #48
markwk commentedSo many subscribing, anyone want to team up on actually doing this for D6?
Comment #49
danielb commentedFYI,
I tried to implement a solution for Drupal 6 some time ago, but wasn't able to complete it.
As this module is abandoned, and I mainly develop in Drupal 7 now, I have created a new module that I'm maintaining here http://drupal.org/project/field_reference
However, it cannot be backported to Drupal 6 as it relies on Drupal 7's entity and field api's.