Programmatically created Membership is assigned to wrong workspace
For Membership associations in DMX there is a special workspace assignment rule: a Membership is assumed to be assigned to the very workspace involved. At the moment this works properly for Memberships created interactively, but not for Memberships created programmatically through the AccessControlService
's createMembership()
call. In the latter case DMX still assigns the Membership to the current workspace, based on dmx_workspace_id
cookie.
This bug was revealed while Mar 18 video chat with @rsc
Thank you very much @rsc for bringing this up!
Note: the DMX standard platform never creates Memberships programmatically. The createMembership()
call is provided for use by 3rd-party plugins. To my knowledge affected are at least the Sign-up and Tendu plugins.