Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Cause this way, doing operations by multiple users is impossible, as the class is singleton.
Comment | File | Size | Author |
---|---|---|---|
0001-engine-do-not-pre-store-the-userId-as-maestro-class-.patch | 1.05 KB | Aron Novak |
Comments
Comment #1
Aron NovakThis one needs work, the current patch breaks the things as the getter is not invoked. The base class has to be modified as well, i have the code, i just need to forge a patch.
Comment #2
_randy CreditAttribution: _randy commentedYou're right -- there is an assumption of who it is we're latching on to in the engine.
I will have to double check, but can't we just directly set the user ID in a new method of setUserID? The default would be current user. I suppose the constructor of Maestro could also be used to set the desired UID.