multiple profiles of the same profile type

The scope of profile2 is to keep it simple and to provide only the features 90% need, thus such additions won't be supported.

I'd actually added this in the data structure at least back in #894028: multiple types.

Is this something that could be added as a submodule? It seems a pretty common use case to me.

>Is this something that could be added as a submodule?
Nop, as the 1-X relation is assumed by the core and actually necessary for most of its UI and API functions. Thus, I don't see how that should work without making the module a complex monster.

Also, if one needs X per user profiles I don't see what's wrong with using "nodes" then - seems like a natural approach for that use-case.

I don't follow the logic of using nodes at all -- changing the cardinality of the entities doesn't change what their purpose for output should be. They should still be profiles rather than content.

Profiles are content too, but a different kind of content.

>a user could add 2 tennis club profile info, no football club profile info and 3 bicycle club...

This is not about user profiles. tennis club profiles are regular site content, thus I'd use nodes. That doesn't mean you can't invent your own entity type for that though, but it doesn't fit in the scope of profile2.

The point is:

The 1-X relation is assumed by profile2 core and actually necessary for most of its UI and API functions. Thus, I don't see how that should work without making the module a complex monster.

Let's keep it simple.

As a workaround, I am looking into field_collections, rather than have a profile with fields, my profile now has a field collection, which contains all the fields my profile was going to contain, now I can add multiple collections of data into the one profile.

Time will tell how well this works out.

I am against using nodes for this because this stuff intrinsically tied to the user as it is information about them and it doesn't feel right using nodes for it, just like usernodes and content_profile felt a bit wrong.

A custom entity is my next attempt if this doesn't work out.

I still have plans to make a 'profile multiple' add-on module. Let me know if your explorations take you that way.

I understand this point of view to keep it simple and to use nodes (or any custom entities) to have multiple "profile" of the same type for one user, but the point is that in my case I must find a solution to have one user with multiple profile2 of the same type.

Here's the situation:

1. I've develop this website based on user+profile2. At the beginning of the project, everything was ok and the website works like a charm now. I have a lot of users+profile2.
2. But now the client wants some users to "administrate" more then one profile2 and do not want the user to log-in/log-out to manage those profile2. And even so, I should find a way to have multiple users with the same email... but that's not the point.

So now I'm on part.2 and I read here and there that I've made a mistake of conception... I understand, and even if you were right, that doesn't solve the problem.

So I think of 2 solutions for now:

1. transform all profile2 into "nodes" and then add a reference field (multiple values) to the user account page. But how to do that in code? or some other way? so I don't have to do it all "by hand"!
2. or alter profile2 to allow multiple profiles of the same type for one user. And I assure you I'd love to spend some time on this solution.

At the end, if anybody has any advice (I mean different from those already posted here :-)) from where I can begin to achieve this task, I'd be grateful.
Hope you understand my point of view.
Thanks in advance.

@joachim Did you ever make any progress on the "profile multiple" module? I could very much use such a thing :)