- Issue created by @snowmountain
- First commit to issue fork.
- 🇺🇸United States snowmountain
After uninstalling Workflow, I was able to save permissions without the error.
A list of installed modules (after disabling Workflow, but all else the same) is https://www.drupal.org/files/issues/2023-09-01/pm-list.txt →
and the error message is https://www.drupal.org/files/issues/2023-09-01/err-perms.txt →
- 🇺🇸United States snowmountain
I see some other modules reporting this same error - it seems it might be due to a core change.
Per https://www.drupal.org/project/field_permissions/issues/3342508#comment-... 🐛 RuntimeException: Adding non-existent permissions to a role is not allowed. Needs review ,
Starting with Drupal 9.3.0, all permissions in a user role must be defined in a module.permissions.yml file or a permissions callback. Other permissions are now considered invalid. This includes permissions from uninstalled modules, permissions that depend on configuration that has been removed (such as a content type), and permissions of obscure origin.
In Drupal 9.3.0 or later, saving a role with an invalid permission will trigger a E_USER_DEPRECATED error. In Drupal 10, it will throw a runtime exception.
- Status changed to Closed: duplicate
10 months ago 11:29am 19 February 2024 - 🇳🇱Netherlands johnv
Thanks,
The problem is fixed and documented here: 🐛 RuntimeException: Adding non-existent permissions to a role is not allowed Fixed