Bug/#214-Fix misnamed 'change_page' permission #215
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
yakky
approved these changes
Jan 14, 2025
|
@jdgoettsch Thanks for this contribution: will release a new version in a few minutes! |
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
Fixes the KeyError that occurs in Django CMS 3.11.8 or later.
PageToolbarMeta.populatetests for a permission namedchangebut the proper permission name ischange_page, causing aKeyErrorto be raised with Django CMS 3.11.8 or later.change_pagehas been used since at least Django CMS 3.4.0, but a refactoring of Django CMS'cms.utils.has_page_permissionfunction in 3.11.8 now results in aKeyErrorbeing raised.References
Fix #214
Checklist
inv lintchangesfile included (see docs)