- 🇺🇸United States drupgirl
This message is quite confusing for end users. It's a "success" message that reads/acts like a failure. Imo the simplest solution is to send this message to the system log and remove the message from the user.
- 🇳🇴Norway gisle Norway
It has been a lot of water under the river since I wrote comment #5 (in 2020), and it turns out that not rebuilding permissions when it is required may in certain situations constitute a security vulnerability. See the related issue 🐛 Does not react to role changes Fixed for background.
It would be much better if somebody could find some time to drill down into this, identify the situations were rebuilding permissions are required, and identify those when it is not. However, until somebody does this (see suggestions for how to proceed in comment #5), these messages stay in the user interface.
- 🇨🇦Canada alienzed
You'd think that, instead of displaying this message to end users who cannot do anything about it, that a Rebuild Permissions would just be triggered, period. No?
- 🇳🇴Norway gisle Norway
Yes. An MR/patch that does trigger rebuild permissions in the right context shall be welcome.
- First commit to issue fork.