Fix: django treebeard 4.5.1 compatibility #6988
Merged
Conversation
This file contains hidden or 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
FinalAngel
approved these changes
Mar 3, 2021
|
great work @Aiky30 |
viktor-yunenko
approved these changes
Mar 5, 2021
gonzalodelgado
pushed a commit
to gonzalodelgado/django-cms
that referenced
this pull request
Mar 24, 2021
This was referenced Apr 6, 2022
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
django treebeard 4.5 introduced breaking changes that changed the check for if a model is being created or not. It appears that the django documentation does not cover the situation seen where the model _state needed to be manually updated.
This fix is now compatible with django-treebeard 4.5.1, 4.5 contained additional breaking changes that 4.5.1 resolves.
Related resources
Checklist
develop