Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analysis of disallowed content #97

Open
ursbraem opened this issue Apr 7, 2022 · 1 comment
Open

Analysis of disallowed content #97

ursbraem opened this issue Apr 7, 2022 · 1 comment

Comments

@ursbraem
Copy link

ursbraem commented Apr 7, 2022

If content_defender is introduced at a later stage in a project, you will run into the situation where already used elements aren't allowed anymore, leading to #72

Feature Idea: Provide a BE Module / Info Page that provides a list of existing, but disallowed elements so they can be either allowed or migrated.

@IchHabRecht
Copy link
Owner

Hi @ursbraem,

Thank you for your request. I think the upcoming command showcased in #72 should solve your problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants