Provide a comparison with core user module + fields [#1006442]

Drupal 7 core recently saw the addition of a nifty option for the user fields: "Display on user registration form." which brings the option of adding fields to user a good alternative to the core profile module and the profile2 module. The profile2 module currently offers an comparison with core's profile module but does not mention that fact that user can simply be turned into pretty basic profile with fields. This is not to say that profile2 has become useless, but it's more to be honest with people evaluating profile2. Depending on your needs, going with core user module + fields might be enough for simple use cases.

Comments

Comment #1

scor commented 23 December 2010 at 21:36

This is a quick draft. profile2 maintainers should correct any mistake:

- allow to make certain fields appear on registration form: user+fields & profile2
- field_group support: user+fields only (profile2 +field_group is broken on user registration form).
- make fields private: profile2 only (and core's profile)
- allow to have several tabs on the user profile form: profile2 only (user+fields will display all the field on the same user/edit form, though you can group them with field_group)
- granular permissions to view/edit own/any profile type: profile2 only

A note should be added to the project page that the use of profile module in core is not recommended and the module is in fact hidden from the modules page (just so newbies don't look for it). Or maybe ditch profile.module entirely and only compare with core's user+field combo.

Comment #2

joachim commented 24 December 2010 at 09:14

There is a difference with optimization, which therefore leads to a conceptual difference.

A field on the user is loaded whenever the user is loaded, so if you add too many fields to the user entity, you'll incur a performance penalty.

Therefore, fields on users should only be data that you will nearly always want whenever you load the user. The user picture (had it been converted to a field, which it hasn't) is a good example. Something like a user signature would be another. This is data that you want to show whenever you show the user on the site, such as where they have posted a comment.

Profile module is for data which you only show on the user's profile page, or in other specific actions (such as addresses, or data from other modules which the user should be able to edit), for which it can be specifically retrieved.

Comment #3

fago

German

Vienna

commented 4 January 2011 at 13:53

Exactly, there is also the conceptual difference of having profiles separated from user account settings - what is necessary for some, especially bigger, sites. Additionally there is the optimization issue as joachim describes very well in #2.

So yes, probably we want to update the project page with a comparison to the user-fields approach and outlining the differences. Also, if there is some documentation about the core profile module dilemma anywhere, we should link that too.

Comment #4

fago

German

Vienna

commented 4 January 2011 at 20:14

Status:

Active

» Needs review

ok, I've tried my best and update the project page. I've not included the performance part as it's probably to technically for the project page, probably there should be a handbook page comparing all available solutions in depth.

Comment #5

scor commented 4 January 2011 at 20:34

Status:

Needs review

» Fixed

The project page looks much better! thanks.

Comment #6

dqd

London | N.Y.C | Paris | Hamburg | Berlin

commented 11 January 2011 at 13:08

Issue tags:

+views, +fields, +Profile 2

Is there a missunderstanding on my side? Or is it true that, individually created fields by last profile 2 build are NOT available on views3-fields in D7? If so, this would be A BIG STEP backwards. Especially because of the fact that, without views, there is no chance to have user-lists with profile images and activity lists and more. Unless you use the deprecated user module + extra fields, which works smoothly with views in the moment.

please correct me, if I am wrong ...

PS: aren't we talking about D7 official release now? (because the issue title)

EDIT: ok I think I got it. THERE WAS A MISSSUNDERSTANDING ON MY SIDE: Either profile nor profile 2 are the best options in future. But I thought I read something about to better use profile 2 in future? Hm, confused ... I think running user module with fields is the only working option in the moment.