Release | April 22, 2013

2.4.1 Released

2.4.1 Released.

With broader testing that came with the 2.4.0 release some issues surfaced and needed a fix:

5 minutes read
  • For USE_I18N=False the testsuite was not adequate and has been updated with some fixes that allow now the use of the CMS with only one language.
  • There where some frotend CSS fixes for the toolbar and admin
  • The check_copy_relations functions introduced in 2.4.0 checks now for abstract classes as well.
  • Non public frontend langauges are now working as advertised.
  • Testsuite has now more than 500 tests :)

That's all. Grab it on pypi :)

Patrick Lauber
contact:

Patrick Lauber

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