When deploying an existing site configuration to a new site installation, the following exception is thrown:
RuntimeException: Adding non-existent permissions to a role is not allowed. The incorrect permissions are "create user_status workflow_transition"
This issue occurs because Drupal is unaware that the dynamic permission has a dependency on the workflow type and attempts to import the permission before the respective workflow type is created.
A similar error was encountered previously in
🐛
RuntimeException: Adding non-existent permissions to a role is not allowed
Fixed
. However, because it was resolved by adding a hook_ENTITY_TYPE_predelete to remove the permission from the user, it only handles the case of a workflow type being deleted.
drush si --existing-configAdd a dependency between the dynamic permission and the respective workflow type so that Drupal resolves the configuration import sequence correctly, as per change-record Permissions can define dependencies →
diff --git a/src/WorkflowPermissions.php b/src/WorkflowPermissions.php
index 04a8730..c909267 100644
--- a/src/WorkflowPermissions.php
+++ b/src/WorkflowPermissions.php
@@ -65,6 +65,9 @@ class WorkflowPermissions implements PermissionHandlerInterface {
and re-enable 'Authenticated user'.</b></i>
Role is enabled to create state transitions. (Determines
transition-specific permission on the workflow admin page.)"),
+ 'dependencies' => [
+ 'config' => ["workflow.workflow.$type_id"]
+ ],
],
// D7->D8-Conversion of 'schedule workflow transitions' permission to "schedule $type_id transition" (@see NodePermissions::create content).
"schedule $type_id workflow_transition" => [
Fixed
1.7
Code
Thanks, added the dependency for all permissions, including trailing comma.
Automatically closed - issue fixed for 2 weeks with no activity.