- Issue created by @kipras729
Although this is a slightly different root cause, I think this may be essentially the same as 💬 RuntimeException: Adding non-existent permissions to a role is not allowed Active . Can you verify?
Renaming a permission in .permissions.yml leads to "RuntimeException: Adding non-existent permissions to a role is not allowed" error.
The old permission name is still in the database's config table and drush role:list, but trying to remove it with drush commands does not help since they do not find it for some reason.
Clearing the cache with Drush also doesn't help.
The only workaround I see is adding the old permission name as a new, separate role in .permissions.yml, uninstalling my custom module, changing .permissions.yml, and re-installing it.
1. Define a permission in .permissions.yml;
2. Go to People->Permissions and assign permission to specific roles;
3. Go to the .permissions.yml file and rename the permission;
4. Go back to People->Permissions, try saving with no or minimal changes.
Active
11.0 🔥
user.module
Although this is a slightly different root cause, I think this may be essentially the same as 💬 RuntimeException: Adding non-existent permissions to a role is not allowed Active . Can you verify?