You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+29-7Lines changed: 29 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,10 @@
6
6
This package is designed to migrate a django CMS 3.5+ project to django CMS 4.0.
7
7
8
8
## What does this package do?
9
-
- Keeps any draft and published content, ensuring that any new draft changes are kept as a new draft version in djangocms_versioning.
9
+
- Keeps any draft and published content, ensuring that any new draft changes are kept as a new draft version in djangocms_versioning.
10
+
- Creates aliases for static placeholder
11
+
- Migrates alias plugins
12
+
- Runs django CMS' migrations
10
13
11
14
## Limitations
12
15
Due to the nature of the changes between django CMS 3.5+ and 4.0 the package will fail to function if an incompatible package is installed.
@@ -27,36 +30,48 @@ Requires knowledge of django CMS Versioning
27
30
### Install the following packages
28
31
The following packages are not yet officially released, they need to be installed directly from the repository. We need your help to make packages v4.0 compatible and to provide documentation for the wider community!
**Warning**: This package can leave your DB in a corrupted state if used incorrectly, be sure to backup any databases prior to running any commands listed here!
Add the migration tool to `INSTALLED_APPS` temporarily. In your `settings.py` make sure that it is listed. You can remove it after the migration process.
64
+
```
65
+
INSTALLED_APPS = [
66
+
...,
67
+
"djangocms_4_migration",
68
+
"djangocms_versioning",
69
+
"djangocms_alias",
70
+
...,
71
+
]
72
+
CMS_CONFIRM_VERSION4 = True
73
+
```
74
+
60
75
If you have a custom user model, you should designate a "migration user" by specifying the user ID in your settings like so:
61
76
62
77
```
@@ -70,6 +85,13 @@ Simply run the following command to run the data migration.
70
85
python manage.py cms4_migration
71
86
```
72
87
88
+
You can ignore warnings of the form
89
+
```
90
+
UserWarning: No user has been supplied when creating a new AliasContent object.
91
+
No version could be created. Make sure that the creating code also creates a
92
+
Version objects or use AliasContent.objects.with_user(user).create(...)
93
+
```
94
+
73
95
## Common solutions for django CMS 4.0 compatibility
74
96
75
97
Import PageContent in a backwards compatible way (Title).
0 commit comments