This repository has been archived by the owner on Nov 27, 2019. It is now read-only.
Adjust migrations for djangoCMS 3.3.0 and 3.3.1 compatibility #259
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.
djangoCMS 3.3.1 introduced a change that by default sets related_name for
cmsplugin_ptr
to%(app_label)s_%(class)s'
. This means that any plugin model which did not explicitly set acmsplugin_ptr
would automatically get this change and prompt django to ask for migrations.To avoid incompatibilities between 3.3.0 and 3.3.1, we decided to explicitly define
cmsplugin_ptr
to match the new format on plugins that need to support both versions.