Release | April 10, 2011

2.2 Feature merge window closed

Last Sunday, April 3rd, the merge window for features closed for 2.2 and we're now in bugfixing only mode.

5 minutes read

The list of new features in 2.2 will be:

  • Plugin media is now handled by django-sekizai
  • There's a public Python API for creating CMS content
  • Group/User based view permissions for CMS Pages
  • Improved frontend editing/toolbar (which will allow an easily extensible toolbar in 2.3)
  • Link plugin does no longer validate URLs
  • Haystack search (implemented in a 3rd party app, not core).

So now we're looking to fix the outstanding issues in 2.2, there's currently 45 issues assigned to the 2.2 milestone on Github, so if you want to help with the 2.2 release, start working on those issues.

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.