Release | April 20, 2015

django CMS 3.1

We're thrilled to announce the release of django CMS 3.1, a significant update to our software. We're proud of the huge collaborative effort that has gone into this release, and very grateful to the community that has contributed it.

5 minutes read

django CMS 3.1 is a consolidation release, building on the progress made in 3.0 and establishes 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.

django-treebeard

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. Testers have reported significantly improved reliability as well as a noticeable increase in tree-related performance. Included migrations will take care of migrating the existing data to the new structure.

Migrations

Django 1.7 is now the primary Django supported version, so South is now an optional dependency and the migration modules has been renamed to conform to a more standard layout. The djangocms_text_ckeditor (v2.5) plugin has already been renamed and the remaining "core" plugins will follow suit in the coming days/weeks.

Goodbye Django 1.4, 1.5, Hello The Future

This release drops support for older Django's which allows use to simplify and improve much of the code-base and prepare for Django 1.8 support. This is planned to come soon.

Much more

There are many other changes and improvements! Please read the release notes for a more complete list and detailed instructions on upgrading to 3.1 from previous releases.

Article

Make Your Django Application Editable

The CMS doesn't need to own your data to make it editable.

Release

django CMS 5.0.11 and 5.1.2 released

Both are patch releases focused on security, stability, and compatibility. We recommend that users of the django CMS 5.0 and 5.1 series upgrade.

Article

The CMS Is Not the Application

Imagine you're building a customer portal. Customers sign in, manage their subscriptions, download invoices, update account details and interact with data from your product.

Then someone asks a perfectly reasonable question: "Can marketing edit the help pages?" You now need a CMS.