Release | February 14, 2015

django CMS 3.0.10 released

Django CMS 3.0.10 is out. This is primarily a bug-fix release aimed at stability for the 3.0.x branch.

5 minutes read

The changelog from the release notes:

  • Improved Py3 compatibility
  • Improved the behavior when changing the operator's language
  • Numerous documentation updates
  • Revert a change that caused an issue with saving plugins in some browsers
  • Fix an issue where urls were not refreshed when a page slug changes
  • Fix an issue with FR translations
  • Fixed an issue preventing the correct rendering of custom contextual menu items for plugins
  • Fixed an issue relating to recovering deleted pages
  • Fixed an issue that caused the uncached placeholder tag to display cached content
  • Fixed an issue where extra slashed would appear in apphooked URLs when APPEND_SLASH=False
  • Fixed issues relating to the logout function

Many thanks to the numerous contributors that have helped us identify these issues and even provided fixes.

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.

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.