It looks like this module is in reality a duplicate of Content Profile. If I understand what it does, it allows the administrator to create a "Profile" entity with several sub-bundles, and make it so that each user can be attached with at most one element of each of those sub-bundles.

This is exactly what Content Profile does if you replace "Bundles of the Profile entity" with "Node types that have been defined as being profiles".

Because Content Profile needs an upgrade path, I suggest we move this work to the Content Profile module itself.

Comments

damien tournoud’s picture

damien tournoud commented
Title: Is this module a duplicate of Content Profile » Is this module a duplicate of Content Profile?
fago’s picture

fago
Primary language German
Location Vienna
commented

I agree that it does the same as content profile, but as you said it's using entities not nodes. Thus content profile wouldn't be the right name for this module. So I see it as its successor.

Still there might be some need for actual "content profile"'s in d7, for that we might use "wrapper nodes" which just display the profile entities. Maybe it would make sense to let content profile for d7 just do the wrapper nodes.

damien tournoud’s picture

damien tournoud commented

My point is: the natural upgrade path for *Content* profile is to become *Entity* profile. Because content profile users will need an upgrade path, it would be better to move all this work to the content profile module and stop unneeded duplication.

joachim’s picture

joachim commented

Over at the roadmap thread some people have said there are still use cases for profiles as nodes.
So we've been thinking content_profile might become a node wrapper on profile2 or something. But I guess that's a smaller use case, and will only happen if enough people who need that work on it.
That case aside, profile2 is very definitely the successor to content_profile; as such we should provide an upgrade path. Where we do it is just a matter of namespace, no? The name content_profile doesn't describe it properly if it's not nodes any more -- plus that system already changed name once before ;)

Btw, Damien, I've been told I should mention address handling to you :)

fago’s picture

fago
Primary language German
Location Vienna
commented
Version: » 7.x-1.x-dev
Status: Active » Closed (won't fix)

see http://drupal.org/project/profile2 and #560324: Content profile: Create upgrade path to profile2 and port to Drupal 7

BenK’s picture

BenK commented

Subscribing

palik’s picture

palik commented

subscribe

liliplanet’s picture

liliplanet commented
Status: Closed (won't fix) » Active

+1 for an upgrade path from content_profile to profile2 please

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (won't fix)
thiruvelan’s picture

thiruvelan commented

Need a easy upgrade path from content profile to profile 2.

fugazi’s picture

fugazi commented

#10 Unfortunately, very late but I really need an upgrade path. -> # 10

I've found so far nothing, can someone help me. I've been in d7 content_profile type and profile2. Sorry for my bad english.

guysaban’s picture

guysaban commented

See: http://drupal.org/project/profile_lite

It will convert Drupal 6 content profile type to Drupal 7 user profile.
It is similar to profile2 but organizes the categories differently.

It would be nice if the two module could combine functionality.

Thereby most people who need the content profile migrate have that and we also could get a choice of how we want to organize categories within the user profiles.