- Issue created by @jsutta
- Status changed to Postponed: needs info
over 1 year ago 8:02pm 9 March 2023 - 🇺🇸United States TR Cascadia
The issue that fixed this problem was #2800749: Support upcasting entity IDs to full entity contexts → , which made large structural changes. As explained in #3088481: Call to a member function id() on string in SystemMailToUsersOfRole.php → , making a quick fix in the user has role condition like your patch does is not acceptable in any case, because it would only "fix" that one condition and would require similar "fixes" in every other condition and action that supports user roles. That is why we took the extra time and effort to fix the structure rather than make a quick fix.
Regardless, we have automated tests to ensure the condition works properly, so if you are still seeing a problem I need to you make sure you have the current -dev version installed and I need you to provide an export of a full rule that uses this condition and has the problem. The most likely explanation is that you have a rule that is passing an invalid role id or user object to the condition, but the only way I can help you is if I see the entire rule export so I can see what you've entered for all the values.
See https://www.drupal.org/docs/contributed-modules/rules-essentials/importi... →
- 🇬🇧United Kingdom adam_b
I think I'm getting the same issue, with a rule I imported from the documentation →
I imported it and changed the role to "administrator". When I run it, a new user is created in the background, but with no role assigned, and the user gets a WSOD.
I've attached the error message and the exported rule.