Follow-up to: #1668292: Move simplified Profile2 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

  1. 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 Profile2 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.

Related issues

Comments

dakala’s picture

Issue summary: View changes

In the latest code for Profile2 - https://github.com/dakala/profile2 (8.x-1.x branch) - this has been implemented by a flag on ProfileType.

mgifford’s picture

Beta1 a good time to open this issue?

dakala’s picture

Sure, we can open it, to track the implementation progress

mgifford’s picture

Status: Postponed » Active

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.