Field Reference: D6 port

I don't have any near-term plans to do it on my own, but I'll commit a patch if you do the work.

Well, 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.

i'll try to have a look at it, but this is not something high on my list

I've packed up and attached what I've done sofar. I doubt it'll be highly useful, but still... prolly won't hurt.

Did 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 :/

yeah i lack time lately
i'll give it a first shot in the next days

subscribe

subscribe

I would like to see this for 6 also. I am not sure how to code it correctly or I would do it myself.

Subscribe. Would love to see this for 6.

I 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.

Well I used nodereference as a reference when implementing fieldreference. I'm not sure much code can be reused though.

What's the current status?

Subscribe, this would be quite usefull.

Does #4 works?

subscribe - a working 6 ver would be woderful ...

Suscribing , defo need this

optgroups don't appear to be supported for selects in 6.x

#306930: Support optgroups in allowed values

Actually, 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.

subscribe

subscribe. any idea if this is going to happen?

+1, subscribing

+1 subscribing

subscribe

This is a must. Subscribing.

+1 Thanks

subscribing

subscribing....

subscribing

Subscribing...

Another subscriber.