Similar to CCK's text and number fields, it would make a lot of sense to support other fields. The "userreference" field type ships with CCK itself, and therefore pretty important to support. The getter/setter callbacks should retrieve/write node objects, while for the import/export callbacks it's probably sufficient to simply return the uid itself.

("Just the uid" because we definitely don't want to deal with differing uids between sites... that's way too much complexity, and really needs to be solved by other means, e.g. unique identifiers, user name comparisons, or assuming that both sites have similar user ids for the same users.)

Comments

jpetso’s picture

Let's not load the user objects, it might not be necessary for all use cases and will require some resources on loading. Let's only return the uid itself, and require the user to load the user by himself if that should be necessary.

jpetso’s picture

Done, will be in beta1.

Matthew Davidson’s picture

Should this be marked closed? It seems to work okay in beta 2.

fago’s picture

Status: Active » Fixed

I think so.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.