Release | July 13, 2016

Maintenance version 3.3.1 of django CMS released

Version 3.3.1 fixes dozens of issues with django CMS providing additional stability for the 3.3.x milestone. It also offers a few notable improvements to UI/UX for end-users and additional capabilities for project developers.

5 minutes read

New and improved

A minor release such as 3.3.1 usually doesn't contain new features, but we did allow an update to the CMS_PLACEHOLDER_CONF setting that offers additional control and functionality to project developers. We also added a warning for users who are leaving the page or closing the plugin modal by pressing ESC to prevent accidental loss of content.

There are also minor but welcome improvements to the documentation and UI/UX that should please users, content managers and developers alike.

Noteable bugfixes

This release has more than 30 bug-fixes. Here are the most notable that some users or developers may be watching out for:

  1. Fixes the default value of the setting CMS_INTERNAL_IPS to reflect the documented behaviour.
  2. Implements numerous permission-related cleanups and fixes.
  3. Fixes a bug that prevented correct operation when using 1Password in Firefox.

Please review the release notes for the full list of changes.

Martin Koistinen
contact:

Martin Koistinen

Article

One operation, three interfaces: a service architecture for django CMS

How shared content operations could support editors, REST integrations, and AI tools.

Learn more

Release

django CMS 5.1.3 and 5.0.13 released

We’re pleased to announce the release of django CMS 5.1.3 and django CMS 5.0.13. Both are maintenance releases focused on fixes and improved robustness.

Learn more

Community news

Inside the Work That Moves django CMS Forward

As the django CMS fellows, we have spent this year so far strengthening that foundation and making new capabilities available to developers and editors.

Learn more