Release | January 24, 2019

django CMS 3.6 Release Candidate 3

A Release Candidate 3 for django CMS 3.6 is now available.

5 minutes read

django CMS 3.6 is on track for release in the coming days. This is the third Release Candidate for version 3.6, to allow our community of users to assess it before the final release.

In addition to the other updates listed below, this RC3 version addresses bugs affecting menu cache.

django CMS 3.6:

  • introduces support for Django 2.0 and 2.1
  • drops support for Django 1.8, 1.9 and 1.10

Take the 3.6 Release Candidate 3 for a test-drive

This Release Candidate is your opportunity to take the new version for a test-drive before its official release. You can install it on your own system or on the Divio Cloud.

Divio Cloud installation

The easiest way to try out django CMS is by creating a new Divio Cloud project, which takes only a couple of minutes.

In the Divio Cloud Control Panel, create a new django CMS project.

Once it has been created, configure its Addons. You will need to specify:

  • django CMS: select version 3.6.0.6 or newer from the Alpha channel of Aldryn django CMS

Then you can Deploy the project.

Install django CMS using pip

Run pip install django-cms==3.6rc3. You should find that updating django CMS to 3.6 in a project already running 3.5.x requires no other changes, as long as you're using compatible versions of Python and Django, and have stopped using deprecated APIs.

What's new

Please see the django CMS 3.6 release notes for more information about what's new and how to upgrade.

We want your feedback

Your feedback is vital and warmly welcomed! All reports, positive and negative, are valuable to us. For technical issues, please use GitHub issues.

Mike Barrett

Article

The next chapter of django CMS starts with our members, past, present and future.

Mike Barrett, elected President of the django CMS Association for 2026 to 2028, thanks Mario Colombo and Joel Burch and sets out three priorities: a more valuable membership, an easier choice for agencies, and meeting in person at DjangoCon Europe.

Article

Hunting Down Quadratic Loops in django CMS

How PR #8913 removed quadratic work from django CMS menus, plugins, and page permissions: a permission-heavy menu on a 4,000-page site went from 11.7 seconds to 105 ms.

Article

One operation, three interfaces: a service architecture for django CMS

How shared content operations could support editors, REST integrations, and AI tools.