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
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,9 @@
3
3
**Warning:** If the migration process fails to complete you will not be able to undo the changes without reloading a database backup. We cannot be held accountable for any data loss sustained when running the commands provided in this project. Please keep a database backup before running any commands provided by this package.
4
4
5
5
## When do I need this package?
6
-
This package is designed to migrate a django CMS 3.5+ project to django CMS 4.0.
6
+
This package is designed to migrate a django CMS 3.5+ project to django CMS 4.0, 4.1.
7
+
8
+
For any later django CMS versions, **first go to django CMS 4.1**, then continue to upgrade.
7
9
8
10
## What does this package do?
9
11
- Keeps any draft and published content, ensuring that any new draft changes are kept as a new draft version in djangocms_versioning.
@@ -12,28 +14,28 @@ This package is designed to migrate a django CMS 3.5+ project to django CMS 4.0.
12
14
- Runs django CMS' migrations
13
15
14
16
## Limitations
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.
17
+
Due to the nature of the changes between django CMS 3.5+ and 4 the package will fail to function if an incompatible package is installed.
16
18
17
19
This may require you to:
18
20
- Fork or copy and modify this package to work with any bespoke requirements your project has (we may accept these changes back for popular packages as a configurable option)
19
21
- Ensure that all installed packages for your project are compatible with django CMS 4. If not, remove them before migrating.
20
22
-`PageFields` in custom models need to have a `related_name` (since page pk change and references need to be updated). If you have page filds with a `related_name="+"`, temporarily give them a related name for the migration.
21
23
22
24
## Prerequisites
23
-
Require knowledge of the changes and new features in 4.0:
25
+
Require knowledge of the changes and new features in 4:
24
26
- New cms app configuration
25
-
- Revised Page, Title (Now named PageContent) and Placeholder relationships
27
+
- Revised `Page`, `Title` (Now named `PageContent`) and `Placeholder` relationships
26
28
27
-
Requires knowledge of django CMS Versioning
29
+
Requires knowledge of [django CMS Versioning](https://djangocms-versioning.readthedocs.io/)
28
30
- Grouper and content model terms
29
31
- Understanding how versioning selects published content
30
32
31
33
### Install the following packages
32
34
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!
0 commit comments