Release | February 9, 2011

django CMS 2.1.1 released

We just released django CMS 2.1.1 to fix an issue brought to light by Django 1.2.5.

5 minutes read

After todays Django 1.2.5 security release, the django CMS AJAX requests stopped working, due to lacking CSRF protection. This critical issue has now been fixed in the 2.1.1 release.

Changes in this version:

  • Fixed CMS AJAX requests not being CSRF protected, thus not working in Django 1.2.5
  • Fixed toolbar CSS issues in Chrome/Firefox

We strongly urge everyone to upgrade to both Django 1.2.5 and django CMS 2.1.1.

Christian Bertschy
contact:

Christian Bertschy

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.

Learn more

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.

Learn more

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.

Learn more