Closed (fixed)
Project:
Profile
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Feb 2018 at 23:46 UTC
Updated:
22 Mar 2019 at 14:49 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
alphawebgroupComment #3
alphawebgrouphere is the patch what fixes this.
Comment #4
alphawebgroupLooks like it's failed.
but.. the question to Maintainers:
is that test correct what is checking the profile creation with uid = NULL?
is it correct by the data integrity?
Comment #5
alphawebgroupComment #6
daggerhart commentedThis makes sense to me. This is exactly how the node module handles the uid base field.
I'm not 100% sure about this step, but the node module also wrote an update hook to ensure the uid field was added to the field storage definition - http://cgit.drupalcode.org/drupal/tree/core/modules/node/node.install#n195.
In the spirit of that, I've added an update hook to the patch which performs the same operations for adding the uid to the entity_keys of the profile module.
Feedback welcome
Comment #7
mglamanI'm not sure why this is needed, we already have the field available.
Looking at that update function.. now I see:
Comment #8
mglamanApparently that line of code is still valid #2981915: Update MenuLinkContent to use EntityPublishedInterface
Comment #9
mglamanNo longer applies, working on a reroll
Comment #10
mglamanReroll!
Comment #12
mglamanOkay, only HEAD failure failed.
Comment #13
bojanz commentedThis also needs to set the "owner" key, like Commerce did, since that is the 8.7 convention.
Comment #14
mglamanThanks @bojanz
Comment #15
mglamanAdds owner key alongside legacy uid.
Comment #17
mglamanAnddddd committed!
Comment #18
eric_a commentedLooks like "menu_link_content" was copy-pasted and not changed. See you in #3038445: Unable to update entity from RC-2?