Release | March 25, 2015

django CMS 3.1 Beta 1 release

We're pleased to announce that django CMS 3.1 Beta 1, the first beta of the next django CMS feature release, is now available on PyPi.

5 minutes read

django CMS 3.1 has been planned largely as a consolidation release, to build on the progress made in 3.0 and establish a safe, solid base for more ambitious work in the future.

In this release we have tried to maintain maximum backwards-compatibility, particularly for third-party applications, and endeavoured to identify and tidy loose ends in the system wherever possible.

The most relevant change is the switch from django-mptt to django-treebeard to handle the tree structure of pages and plugins: this will greatly benefit users with large number of pages and issues with concurrent editing. Included migrations will take care of migrating the existing data to the new structure.

Django 1.7 is now the primary Django supported version: south is now an optional dependency and the migration modules has been renamed to conform to a more standard layout.

Please check the Release notes for detailed information on upgrading.

Django 1.8 support is planned, and will be delivered after the 3.1 final release in a future patch version.

If all goes well and no critical issues are reported, a release candidate is expected on April 2nd, with a final release on April 10th.

All users are encouraged to test this version on their project and report any encountered issue to make 3.1 even more stable for everybody.

Go and test it while it's hot!

Release

django CMS 5.1 is here: easier setup, flexible deployments, and a fresh editing experience

This release reduces friction across the whole project lifecycle: creating a new project, adding django CMS to an existing Django application, configuring larger deployments, controlling which plugins editors can use, and working with the CMS every day.

Release

django CMS 5.0.9 released: security, accessibility, and stability improvements

This release addresses three medium-severity security vulnerabilities and includes improvements to accessibility, Django compatibility, permissions, Content Security Policy support, and general editor stability.

Case Studies

How we built our professional services digital platform using django CMS

Compound Partners is a UK digital consultancy specialising in audience-centric user experience and content architecture for professional services firms. Fifteen years ago, a developer's recommendation pointed us at django CMS. Today, our entire business is built on it.