feat: hide legacy features in v4 admin/toolbar #7521
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Some legacy features are still available in django CMS v4 to allow for migration. This PR hides their admin entries unless the setting
CMS_HIDE_LEGACY_FEATURESis set toTrue.So far it hides the static placeholder admin. Static placeholders are replaced by static aliases of the djangocms-alias package.
This PR is draft in case other features have to be hidden, too. Please do comment if you find a legacy v3 feature visible in django CMS 4.
Related resources
Checklist
develop-4