-
Notifications
You must be signed in to change notification settings - Fork 24
Description
1. Check if the djangocms_blog Post table exists
2. Check that all migrations in OUR djangocms_blog app have been applied
3. Migrate each model from djangocms_blog to djangocms_stories
4. Copy many-to-many relationships
5. Update generic relations
6. Drop all djangocms_blog tables from the database
7. Remove djangocms_blog migration records
8. Adjust apphooks
OK
Applying djangocms_stories.0003_alter_post_options_alter_postcontent_options_and_more... OK
Applying djangocms_versioning.0016_auto_20230505_0934... OK
Applying djangocms_versioning.0016_alter_version_content_type... OK
Applying djangocms_versioning.0017_merge_20230514_1027... OK
Processing site: 3
Processing Language: en Plugin count: 0
Processing site: 1
Processing Language: en Plugin count: 7
...\env\Lib\site-packages\djangocms_4_migration\management\commands\migrate_alias_plugins.py:207: UserWarning: No user has been supplied when creating a new AliasContent object. No version could be created. Make sure that the creating code also creates a Version objects or use AliasContent.objects.with_user(user).create(...)
alias_content = AliasContent.objects.create(
Deleting old plugin: 74424
Traceback (most recent call last):
File "...\env\Lib\site-packages\django\db\backends\utils.py", line 105, in _execute
return self.cursor.execute(sql, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "..\env\Lib\site-packages\django\db\backends\sqlite3\base.py", line 360, in execute
return super().execute(query, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sqlite3.OperationalError: no such table: djangocms_blog_latestpostsplugin