AIRAVATA-3698 management command to fix up the content type id in page revision json #186
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.
The content type id in the wagtailcore_pagerevision.content_json column doesn't match the page's actual content type. when the page was imported from a wagtail export. The reason is that the content type ids were different in the Django instance where the Wagtail pages were developed and exported from. This causes at least a couple problems:
This PR adds a management command (fix_page_revision_content_type) that will programmatically look for and fix up any content_json that has a content_type id that doesn't match the page's actual content type. Additionally, this PR automatically calls fix_page_revision_content_type after loading a Wagtail export. This should prevent this issue from resurfacing.