I was deleting an older config page that wasn't necessary anymore and I noticed when trying to save an unrelated entity, I got an error related to orphaned permissions on fields that no longer exist because the config page was deleted.

I ended up editing the config files that had these orphan permissions - they were user.role.rolename files. I also found a single token to remove as well, during this process.

This exercise was actually useful to see where deleting the config page might have inadvertently impacted something else. So, if a fix were to be implemented, I think it should list what would change. Since deleting a config page that was in use with custom field permissions is unusual, stumbling upon this post will probably be sufficient.

Issue fork config_pages-3454702

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

davemaxg created an issue. See original summary.

davemaxg’s picture

davemaxg commented
Issue summary: View changes

shumer made their first commit to this issue’s fork.

shumer opened merge request !71

  • shumer committed 86bc18e2 on 4.0.x 
    Issue #3454702: Revoke config page permissions when the type is deleted
shumer’s picture

shumer commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.