Framework Third-party distributions of Django For distributors Glossary Release notes Final releases 3.0 release 2.2 release 2.1 release 2.0 release 1.11 release 1.10 release 1.9 release 1.8 release 1.7 release cadence Deprecation policy Supported versions Release process Django Deprecation Timeline 4.0 3.1 3.0 2.1 2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The Then at the Python prompt, try to import Django: >>> import django >>> print(django.get_version()) 3.0 You may have another version of Django installed. That’s it! That’s it – you can now move onto the

Then at the Python prompt, try to import Django: >>> import django >>> print(django.get_version()) 3.0 You may have another version of Django installed. 2.2.5 That’s it! That’s it – you can now move isn’t, you’ll get an error telling “No module named django”. This tutorial is written for Django 3.0, which supports Python 3.6 and later. If the Django version doesn’t match, you can refer to the tutorial ˓→applied. Run 'python manage.py migrate' to apply them. April 06, 2021 - 15:50:53 Django version 3.0, using settings 'mysite.settings' Starting development server at http://127.0.0.1:8000/ Quit the server

django CMS? CHAPTER 4 Release Notes This document refers to version 3.0.19.dev1 Warning: Version 3.0 introduces some significant changes that require action if you are upgrading from a previous version (with Django 1.6.X and Django 1.7.X) to support versioning of your content. Note: As of django CMS 3.0.x, only the most recent 10 published revisions are saved. You can change this behaviour if required file that can be used with pip to install django CMS and its dependencies: # Bare minimum django-cms>=3.0 # These dependencies are brought in by django CMS, but if you want to # lock-in their version, specify

django CMS? CHAPTER 4 Release Notes This document refers to version 3.1.8.dev1 Warning: Version 3.0 introduces some significant changes that require action if you are upgrading from a previous version higher (Only required up to Django 1.6) • django-classy-tags 0.6.2 or higher • django-treebeard 3.0 • django-sekizai 0.8.2 or higher • djangocms-admin-style • An installed and working instance of reversion wiki in order to make sure that the package versions are compatible.) Note: As of django CMS 3.0.x, only the most recent 10 published revisions are saved. You can change this behaviour if required

emphasis on automated testing Release Notes This document refers to version 3.3.4 Warning Version 3.0 introduces some significant changes that require action if you are upgrading from a previous version 0.9 release notes 3.0.8 release notes 3.0.7 release notes 3.0.6 release notes 3.0.3 release notes 3.0 release notes 2.4 release notes 2.3.4 release notes 2.3.3 release notes 2.3.2 release notes 2.3 release [https://github.com/etianen/django-reversion] 1.10 to support versions of your content Note As of django CMS 3.0.x, only the most recent 10 published revisions are saved. You can change this behaviour if required

tested, or is known to be incompatible. django CMS Python Django 3.8 3.7 3.6 3.5 3.4 3.3 2.7 2.6 3.0 2.2 2.1 2.0 1.11 1.10 1.9 1.8 1.6 1.4 3.7.x ✓ ✓ ✓ ✓ ✓ ✓ ✓ ⨯ ✓ LTS ✓ ✓ LTS ⨯ ⨯ ⨯ ⨯ ⨯ 3.7.0 ⨯ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ⨯ x LTS ✓ ✓ LTS ⨯ ⨯ ⨯ ⨯ ⨯ django CMS Python Django 3.8 3.7 3.6 3.5 3.4 3.3 2.7 2.6 3.0 2.2 2.1 2.0 1.11 1.10 1.9 1.8 1.6 1.4 3.6.x ⨯ ✓ ✓ ✓ ✓ ✓ ✓ ⨯ x ✓ ✓ ✓ ✓ ⨯ ⨯ ⨯ ⨯ ⨯ 3.5.x ⨯ ✓ ✓ ✓ ✓ ✓ ✓ ⨯ the frontend editor only after saving the relevant instance. Admin Integration Changed in version 3.0. Your model with PlaceholderFields can still be edited in the admin. However, any PlaceholderFields

2.6 3.0 2.2 2.1 2.0 1.11 1.10 1.9 1.8 1.6 1.4 3.7.x ✓ ✓ ✓ ✓ ✓ ✓ ✓ ⨯ ✓ LTS ✓ ✓ LTS ⨯ ⨯ ⨯ ⨯ ⨯ 3.6.x ⨯ ✓ ✓ ✓ ✓ ✓ ✓ ⨯ x ✓ ✓ ✓ ✓ ⨯ ⨯ ⨯ ⨯ ⨯ django CMS Python Django 3.8 3.7 3.6 3.5 3.4 3.3 2.7 2.6 3.0 2.2 2 the frontend editor only after saving the relevant instance. Admin Integration Changed in version 3.0. Your model with PlaceholderFields can still be edited in the admin. However, any PlaceholderFields mymodel_instance.my_placeholder language 'en' %} Adding content to a placeholder Changed in version 3.0. Placeholders can be edited from the frontend by visiting the page displaying your model (where you

been tested, or is known to be incompatible. django CMS Python Django 3.9 3.8 3.7 3.6 3.5 3.4 3.2 3.1 3.0 2.2 2.1 2.0 1.11 4.0.x ✓ ✓ ✓ ✓ × × ✓ ✓ ✓ ✓ × × × 3.9.x ✓ ✓ ✓ × × × ✓ ✓ ✓ ✓ × × × 3.8.x × ✓ ✓ ✓ ✓ × the frontend editor only after saving the relevant instance. Admin Integration Changed in version 3.0. Your model with PlaceholderFields can still be edited in the admin. However, any PlaceholderFields mymodel_instance.my_placeholder language 'en' %} Adding content to a placeholder Changed in version 3.0. Placeholders can be edited from the frontend by visiting the page displaying your model (where you

historical models may be out of sync with the applied database schema. To keep compatibility with 3.0 and 3.x you can force the data migration to run before the django CMS migration that creates treebeard templates used by external applications, use static_placeholder instead. CMS_TEMPLATE New in version 3.0. CMS_TEMPLATE is a context variable available in the context; it contains the template path for CMS cms template so the application template can dynamically import it. render_model New in version 3.0. render_model allows to edit the django models from the frontend by reusing the django CMS frontend

tested, or is known to be incompatible. django CMS Python Django 3.9 3.8 3.7 3.6 3.5 3.4 3.2 3.1 3.0 2.2 2.1 2.0 1.11 4.0.x ✓ ✓ ✓ ✓ × × ✓ ✓ ✓ ✓ × × × 3.9.x ✓ ✓ ✓ ✓ × × ✓ ✓ ✓ ✓ × × × 3.8.x × ✓ ✓ ✓ ✓ compatibility table 39 django cms Documentation, Release 3.9.0 Admin Integration Changed in version 3.0. Your model with PlaceholderFields can still be edited in the admin. However, any PlaceholderFields mymodel_instance.my_placeholder language 'en' %} Adding content to a placeholder Changed in version 3.0. Placeholders can be edited from the frontend by visiting the page displaying your model (where you