Release | April 27, 2016

django CMS packaging issue and patch

This patch addresses a packaging error in yesterday's django CMS release.

5 minutes read

Unfortunately yesterday's releases of django CMS (3.2.4,  3.1.6 and 3.0.17) contained a packaging error, and included old South migrations and .pyc files.

Our latest releases (3.2.5, 3.1.7 and 3.0.18) are on PyPI and fix the problems. If you had trouble with one of the releases from yesterday, you should find that upgrading to the latest version is all you need to do.

We apologise for the inconvenience.

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.