search

PECE-project / drupal-pece

PECE development repository
GNU General Public License v3.0
21 stars 28 forks source link

Migrate Profile2 fields (to Profile in Drupal 10) #353

Open mlncn opened 11 months ago

mlncn commented 11 months ago

Multiple profiles are not used (and if they were or are wanted we could use user bundles rather than Profile module).

Profile2 fields and their content should be migrated to the user entity's default 'user' bundle.

mlncn commented 11 months ago

@dinarcon on further looking into this with @MegaKeegMan the current sites make a clear distinction between private "Account" data in one tab and public "Profile" data in another tab, both saved separately. Even the e-mail address under Profile can be different from that under account. Since Profile module supports migrating from Profile2, maybe we should keep profile? Probably easier to migrate and get the desired functionality, at the cost of a little more to maintain in the long-term.

mlncn commented 10 months ago

Profile | Drupal.org

MegaKeegMan commented 10 months ago

This issue has just become a high priority task, since I just discovered that attempting to add a user results in a WSOD.

mlncn commented 9 months ago

The fatal error is fixed and as expected it was not related to migration or old data or anything: Drupal 10.1: fatal error on account creation [#3371850] | Drupal.org

MegaKeegMan commented 9 months ago

Confirmed. As of 0f1abdf54b106ee4e60be0b24240f3740078ac3b (just a composer update), creating users does not cause a fatal error.

MegaKeegMan commented 7 months ago

For now, let's make sure that each user can only have one profile.

MegaKeegMan commented 7 months ago

There are pece specific permissions for profile. Why were these done and can we get rid of them?

MegaKeegMan commented 7 months ago

It looks like the pece profile permissions are more granular, providing permissions like "Update any profile" and "Update own profile". Aren't these usually handled by the profile module?