Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.With the Profile2 module installed, users may be merged which do not have profiles or do not have profiles with all the currently-defined fields present in the particular user(s) profile(s).
When a user is created by the UI, at least with the Profile2 configuration I'm using, all profiles are defined and all fields are present but have empty values. If a user is created programmatically or is created manually when the current profile2 configuration isn't defined, a profile may be missing. I also suspect (but haven't confirmed) that adding a field to a profile will not cause profile2 to return an empty field for it for a pre-exisiting user.
There is code which handles some but not all cases. The merge option in particular is not well protected against missing data. The effect may be a loss of profile2 data after the merge.
This is a somewhat different issue from the related issue, where the error seems to be occuring much earlier, before the merge specification is defined by the user.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | usermerge-profile_missing_merge-2961130-1.patch | 2.57 KB | danchadwick |
Comments
Comment #2
danchadwick commentedProfile2 user merge will now create profiles if needed in all cases and will check for missing fields during merge option. In cases where the profile is freshly-created, there are no fields (i.e. the field keys are missing from the profile object).