Let's go with the same one that is selected based on the vetting at #1555038: Use core Entity API for User profile fields.

Comments

sheldonkreger’s picture

sheldonkreger commented

It still seems there is some debate in the above thread. Has a decision been made?

cafuego’s picture

cafuego commented

I've not gotten a COD 7 dev site setup yet to play with, so I'll ask... does (or will) COD7 use Signup? There is a signup_profile module at http://drupal.org/project/signup_profile which integrates and allows for profile fields to be displayed in the signup UI.

That is all for D6 btw.

It supports core profile and can probably be ported to D7. There is a semi-working patch that makes it support content_profile (which has turned into profile2 for D7).

twardnw’s picture

twardnw commented
Issue tags: +da_drupalcon

COD7 is going to use Entity Registrations

cafuego’s picture

cafuego commented

Cool, so the user's profile fields will be added to registrations via Field Collection. I'll have a play with that and see what/how that works with core profile and profile2.

ezra-g’s picture

ezra-g commented

@cafuego What have you learned from that investigation?

I suggest we proceed assuming well use the core entity/field system for user profiles.

cafuego’s picture

cafuego commented

@ezra-g I haven't had time yet to look at profile2, I'm afraid.

However, I did have a scan through some of the arguments for profile2 in #1555038: Use core Entity API for User profile fields and although I agree that different profile types for different users can be very useful for many Drupal sites, I don't think it actually makes life easier when trying to run an event. If anything, it adds complexity where none is needed.

So I concur that core profiles are the way to go :-)

ezra-g’s picture

ezra-g commented
Status: Active » Fixed

We've been using core entity fields via commons_profile_base for months now.

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