Release | December 24, 2010

django CMS 2.1 Release Candidate 1 has been released!

The first Release Candidate for the Django-CMS 2.1 was just released and is ready for testing.

5 minutes read

The first Release Candidate for the Django-CMS 2.1 was just released and is ready for testing.

Please keep in mind that this is a release candidate, and not a final release yet!

Documentation: [http://django-cms.rtfd.org](http://django-cms.readthedocs.org/en/support-3.0.x/)

Source: [https://github.com/divio/django-cms/tree/2.1.0.rc1](https://github.com/divio/django-cms/tree/2.1.0.rc1)

Please report any issues you find with this release to our issue tracker at https://github.com/divio/django-cms/issues, thank you.

This second Release Candidate fixes a few bugs found in 2.1 RC1 as well as a compatibility problem with Django 1.2.4 which was released shortly after RC1.

The bugs fixed in RC2 are:

  • #621: Page changelist in admin is incompatible with Django 1.2.4 when using multiple sites
  • #624: Saving pages with a language not available to the site currently being browsed, but available to the target site of the page
  • #631: MultilingualURLMiddleware does not work with single-quoted urls in templates
  • #630: Pages cannot be added if CMS_MODERATOR is False

There are currently no known issues with RC2.

So what's new in 2.1?

  • Frontend Editing! You can edit your contents directly on the site, as an alternative to the more abstract admin panel.
  • Better integration of 3rd party applications! It is now easier then ever to integrate any 3rd party Django applications into your CMS or make your Django application CMS-Ready.
  • "Placeholders" It is now possible to use the Django-CMS Plugin based content architecture in any Django model using the new Placeholder Fields! This even comes with full blown frontend editing.
  • Menu Refactor The menu code has been strongly refactored since 2.0 and it is now easier to extend and alter the menus.
  • Better Docs, Better Tests, Better Code Our documentation is now hosted on the amazaing readthedocs.org and was improved vastly and is still being improved until 2.1 final. On top of that our testing infrastructure, our test suite and our test coverage has improved significantly as well. And in the process of fixing a lot of bugs, we have also improved the readability and maintainability of the Django-CMS codebase to make it easier for new developers to get around.
  • And lots more! Wishing you a merry Christmas in the name of the Django-CMS core developers team, Jonas Obrist

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.