The current implementation of the user entity uses the old user context in order to get a custom form. The old user context is currently not compatible with the entity relationship plugins, which sends in the unique identifier as data to to context, not the fully loaded context.
Another problem with the current implementation is that the user context and the entity:user context "collides" in the views_content configuration. entity:user is the one that is used, but when you try to use a user property from the user context as an argument, it doesn't work.
This patch makes the user context load the user if a numeric id is provided as data. It also changes the type of the context to entity:user, since the user context is just used to provide a custom form anyway. This solves the problem with the context collisions.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | fix-user-context.patch | 867 bytes | fabsor |
| fix-user-context.patch | 842 bytes | fabsor |
Comments
Comment #1
fabsor commentedSetting status.
Comment #2
fabsor commentedI realised that this broke some other stuff related to required contexts. The attached patch uses exactly the same parameters as the entity context to create the context object and this seems to work everywhere.
Comment #3
triskele commentedThanks for the patch - this did the trick for me. User picture doesn't seem to display still though, so I'm wondering why that is. Investigating.
Comment #4
itangalo commentedDid the trick for me too. Good stuff – it allows me to continue recording screencasts for Page manager. :-)
Comment #5
itangalo commentedI checked the user picture as well – it displays fine for me.
Setting this patch to RTBC.
Comment #6
merlinofchaos commentedPushed, committed.