0

The profile core module is being deprecated in D7. It exists and operates in D7, but is hidden and can only be enabled with drush or a custom module. Drupal.org recommends that users now use Profile2, a custom module, but my attempts to do so have met with WSOD on several attempts. In fact, after enabling the module, it will crash the site if you try to disable it. The problem links to a core issue, but even with the recommended patch, Profile2 still has other problems I have not been able to correct yet.

In the meantime, I enabled Profile, and it has desirable features I would like to implement. My concern is that whatever I do may be lost in the future. Since I cannot load Profile2, I do not know if it builds on Profile or I will have to reconstruct everything later.

3
  • What is causing your WSOD? If you haven't done so, follow the instructions at drupal.org/node/158043 to resolve the problem.
    – BetaRide
    Jan 26, 2012 at 19:13
  • Thanks for asking. Profile2 is causing it, but by circumstances outside their control. The cache clearing sequence has a problem that they have been chasing for months. There was a recent patch that fixes that, but as soon as I tried again, apparently profile 2 had not installed fields in the database, it needs. I have a report in with them.
    – Ashlar
    Jan 26, 2012 at 19:29
  • 1
    you can now extent the core user fields in D7 and might not need profile2 at all. Do you have any special requirements?
    – uwe
    Jan 26, 2012 at 19:31

1 Answer 1

1

First of all, it's important to understand something MotoTribe has already mentioned. The most important functionality of "Profile" is now in for Drupal 7 new "users are entities" concept. Since this allows you extend users with fields, the profile module was considered redundant.

If I recall correctly, the main reason for it remaining in Core, was as a transition path from D6 Profile. In D8 I don't believe Profile will exist at all, and since it's already deprecated, I very much doubt there will be an upgrade path from D7 profile.

If we instead follow the trail of issues that follow from yours on the Profile2 queue, we find a Core issue, which is so far advanced that it has been applied to D8, and applies cleanly against D7 with full test coverage. I would apply that D7 patch, and try with Profile2 again.

1
  • Thanks, I did. I can now disable the module without crashing the site, but run into a database table problem I think may be Profile2. All I am trying to do is understand what these modules did to see if I need their functionality to make a user profile work better. I've enabled Profile to look at it and it handles some things such as private and public information, input forms etc. which would be nice to use. Without it, it looks like putting together a custom module may be the only way.
    – Ashlar
    Jan 26, 2012 at 21:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.