- Issue created by @scottop
I am upgrading from Drupal 9.5.4 to Drupal 10. The Upgrade Status module tells me what has to be fixed before I upgrade, and it flags bad permissions that will cause a runtime error in Drupal 10. It took a while to figure, but was eventually reproducible.
Create a custom content type. Give it some Entity Print permissions. Delete the content type. The permissions will not be deleted from the config database, and will throw an error in the Update Permissions database.
Workaround is to remove all of the permissions (checkboxes) in the Entity Print permissions table before you delete the content type. But you should not have to. When you delete a content type, it tells you the configurations it will modify or delete, but Permission or Access is not among those listed. There is probably just some further specification that needs to be made of "when you delete a content type, remove these permissions."
Specify the Access Config's that you modify when installing and mark them to be removed when a content type is deleted.
Active
2.13
Code