machristie opened a new pull request, #186: URL: https://github.com/apache/airavata-django-portal/pull/186
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: - it causes an issue when migrating from wagtail 3.0 -> 4.0 (see [comment on AIRAVATA-3698](https://issues.apache.org/jira/browse/AIRAVATA-3698?focusedCommentId=17735463&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17735463)) - it causes an issue with saving revisions, causing them to sometimes fail to save which can result in history and data loss. 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
