up” anything that hasn’t already been matched by a previous pattern. Now run the application’s migrations: python manage.py migrate polls At this point you should be able to log in to the Django admin # the newly-created application __init__.py admin.py models.py migrations.py tests.py views.py static/ manage.py project.db requirements [https://docs.djangoproject.com/en/2.2/ref/models/instances/#django.db.models.Model]. Create and run migrations: python manage.py makemigrations polls_cms_integration python manage.py migrate polls_cms_integration

up” anything that hasn’t already been matched by a previous pattern. Now run the application’s migrations: python manage.py migrate polls At this point you should be able to log in to the Django admin media/ mysite/ polls_cms_integration/ # the newly-created application __init__.py admin.py models.py migrations.py tests.py views.py (continues on next page) 16 Chapter 4. Software version requirements and release Django/Python compatibility table 17 django cms Documentation, Release 3.10.0 Create and run migrations: python manage.py makemigrations polls_cms_integration python manage.py migrate polls_cms_integration

up” anything that hasn’t already been matched by a previous pattern. Now run the application’s migrations: python manage.py migrate polls At this point you should be able to log in to the Django admin # the newly-created application __init__.py admin.py models.py migrations.py tests.py views.py static/ manage.py project.db requirements [https://docs.djangoproject.com/en/2.2/ref/models/instances/#django.db.models.Model]. Create and run migrations: python manage.py makemigrations polls_cms_integration python manage.py migrate polls_cms_integration

up” anything that hasn’t already been matched by a previous pattern. Now run the application’s migrations: python manage.py migrate polls At this point you should be able to log in to the Django admin media/ mysite/ polls_cms_integration/ # the newly-created application __init__.py admin.py models.py migrations.py tests.py views.py static/ manage.py project.db requirements.txt Add it to INSTALLED_APPS Next cms.models.pluginmodel.CMSPlugin (or a sub-class thereof) and not models.Model. Create and run migrations: python manage.py makemigrations polls_cms_integration python manage.py migrate polls_cms_integration

install mysqlclient # for MySQL or MariaDB This is to ensure that you do not accidentally run migrations on a django CMS version 3 database. This can lead to corruption since the data structures for the CMS_CONFIRM_VERSION4 = True to your django CMS version 3 project unless you know what you are doing. Just running migrations can lead to data loss. Warning To migrate a django CMS version 3 project to version 4 you can have assist the migration from v3 to v4. It is not (yet) officially supported. Database tables Now run migrations to create database tables for the new applications: Sekizai Django Sekizai [https://github.com

migrating a version 3 project Add to settings.py: This is to ensure that you do not accidentally run migrations on a django CMS version 3 database. This can lead to corruption since the data structures for the CMS_CONFIRM_VERSION4 = True to your django CMS version 3 project unless you know what you are doing. Just running migrations can lead to data loss. Warning To migrate a django CMS version 3 project to version 4 you can have Postgres pip install mysqlclient # for MySQL or MariaDB CMS_CONFIRM_VERSION4 = True Now run migrations to create database tables for the new applications: Sekizai Django Sekizai [https://github.com

unicode issues • Fix a missing argument in ModelAdmin • Fix a bug in WymEditor handling • Fix bugs in migrations • Fix bug in language fallback • Minor documentation fixes 1.3 2.4 release notes 1.3.1 What’s new require action if you are upgrading from a previous version. You will need to read the sections Migrations overhaul and Added a check command below. Introducing Django 1.5 support, dropped support for Django required versions. Migrations overhaul In version 2.4, migrations have been completely rewritten to address issues with newer South releases. To ease the upgrading process, all the migrations for the cms application

unicode issues Fix a missing argument in ModelAdmin Fix a bug in WymEditor handling Fix bugs in migrations Fix bug in language fallback Minor documentation fixes django cms 2.4.3-support documentation » require action if you are upgrading from a previous version. You will need to read the sections Migrations overhaul and Added a check command below. Introducing Django 1.5 support, dropped support for Django required versions. Migrations overhaul In version 2.4, migrations have been completely rewritten to address issues with newer South releases. To ease the upgrading process, all the migrations for the cms application

’menus’, helper for model independent hierarchical website navigation • ’south’, intelligent schema and data migrations • ’sekizai’, for javascript and css management Also add any (or all) of the following plugins Using South with django CMS South is an incredible piece of software that lets you handle database migrations. This document is by no means meant to replace the excellent documentation available online, but syncdb command, simply run manage.py schemamigration --initial . This will create a new migrations package, along with a new migration file (in the form of a python script). 2. Run the migration

’menus’, helper for model independent hierarchical website navigation • ’south’, intelligent schema and data migrations • ’sekizai’, for javascript and css management Also add any (or all) of the following plugins Using South with django CMS South is an incredible piece of software that lets you handle database migrations. This document is by no means meant to replace the excellent documentation available online, but syncdb command, simply run manage.py schemamigration --initial . This will create a new migrations package, along with a new migration file (in the form of a python script). 20 Chapter 2. Getting