Follow-up to: #1668292: Move simplified Profile module into core
Problem
- The is a 1:1 relationship between a user account and each profile (type) currently, but certain profile types may need to be multiple (1:n).
Proposed solution
-
Add a property/flag to ProfileType that indicates whether users may create multiple instances of the profile type.
Quoting @fago from #1668292-84: Move simplified Profile module into core:
This could be an optional validation constraint, or an additional entity reference for optional attaching the profile to another entity (configured per bundle). This reference could be used for making sure there is just 1 profile per attached entity + it can be the base for adding in profile2 display extra-field integration or user-register extra-form integration.
Comments
Comment #1
dakalaIn the latest code for Profile2 - https://github.com/dakala/profile2 (8.x-1.x branch) - this has been implemented by a flag on ProfileType.
Comment #2
mgiffordBeta1 a good time to open this issue?
Comment #3
dakalaSure, we can open it, to track the implementation progress
Comment #4
mgiffordComment #17
smustgrave CreditAttribution: smustgrave at Mobomo commentedOn a decision about if profile will be added to core
Comment #18
smustgrave CreditAttribution: smustgrave at Mobomo commentedWas determined to keep profile in contrib in #1668292: Move simplified Profile module into core
Comment #19
smustgrave CreditAttribution: smustgrave at Mobomo commented