Hey Joachim- this is a great module and I hope to incorporate it at some point.

I notice that in the module file itself, one of the missing requirements was phrased a bit differently: 'support for more than one field.'

So can the module deal with the *same* user reference field if it's reused on multiple node types, or must there only be exactly one user reference field, used once, period?

Comments

joachim’s picture

joachim commented

> So can the module deal with the *same* user reference field if it's reused on multiple node types

Probably not. At least, there's a bit of the CCK API I use where there's a ->type property for node type, and I'm not sure what happens there if the field is on multiple node types.

All this is stuff that can be fixed, it's just a question of digging a bit more into what CCK gives you back and dealing with the different possible cases. It's just that it was beyond the spec for the client this module was written for -- hence why I call this a 'half-baked module'.

If you want to work on this functionality, I can either review your patches or make you a co-maintainer :)

joachim’s picture

joachim commented

For reference: #710480: type_name key in content_fields() array is unreliable.