Maintainer needed for D7 versions of nodereference / userreference

They are not the only modules. There is fieldgroup and content_permissions and also a need for a module to host a contrib field upgrade path. There is also a need to support some field features that are not in core (like using php code to create an allowed values array, something core will not do).

CCK will still be needed in D7, we cannot get rid of it.

There is another issue about whether nodereference and userreference should become separate modules, which can be hashed out there.

I guess I should say I think it will still be needed. We can't be sure until we get the upgrade path written and see what additional functions/features are needed to support fields being upgraded from D6.

Hi Karen. As many other are we looking at starting sites launching in 2011 in Drupal 7 but are still a bit confused regarding user and node –reference. They did not get into core so they need to be provided by stand alone modules right?

Nodereference and Userreference are in the D7 version of the CCK module already.

For the record, I consider noderef and useref modules for D7 as "maintainer wanted".
Their current code in CCK HEAD works as a straight D7 port (minus the 'views mode' - referenceable nodes/users defined by a View).
I strongly feel that they would be better off as separate modules in D7. I do not intend, however, to maintain contrib modules myself in the D7 cycle. So - candidates welcome.

Should there just be a single entity reference module created instead? Has anyone looked at this possibility?

If it is feasible, this would probably replace taxonomy, user and node reference widgets and be instantly usable for other types too.

[edit]
The node reference already appears to have full base functionally outside of CCK. Big +1 for moving it to its' own project!

@Alan D. : see the beginning of #533222: node and user reference fields in D7 - maintainer needed.

@yched Thanks.

I skimmed the middle of that thread a bit too fast... #533222: node and user reference fields in D7 - maintainer needed #44 has a piece on the entity based module bit. Staying with the KISS for the meantime :) I'd do the same thing! Some interesting projects have been started, but hopefully there will be a lightweight solution. Maybe after I finish my vacation in 6 months....

In regards to separate modules? The general feeling that I got when skimming these threads was that KarenS is for a CCK wrapper project for all of the left overs; you seem to be for separate projects, possibly with a CCK dependency. It is a bit unclear of the direction. Of the 100 or so sites we have done, about 80% have a node reference, 3% have a user reference, about 2% have permissions. For our perspective, having an independent module for each would be the best use case. Yes, there is code duplication, but the node reference module is only ~800 lines. Clarification would help potential maintainers with the exact nature of the project that they are about to volunteer for.

I am not 'for' or 'against' having these as separate projects. The point I was making is that there are various bits besides these modules that don't exist anywhere else yet that someone has to take responsibility for. And there is currently code for nodereference and userreference in the cck module. So the code *does* exist, which some people seem confused about. I keep hearing discussion that sounds like people don't think there is a D7 version of that code, but there is.

Plus the D6-D7 migration code has to live somewhere and currently that is in cck.

If someone wants to take these things over, that's fine, but they need to be somewhere in the meantime. And I personally don't want to end up having to maintain and/or download a dozen separate projects, but I guess that is likely to happen anyway.

Should we perhaps have an wiki-page to write up a battle plan and reach some kind consensus? I feel the discussion is a bit fragmented. At #70 in this issue #533222: node and user reference fields in D7 - maintainer needed is there quite good summary and also provide some suggestions.