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.

Mike Barrett

Article

The next chapter of django CMS starts with our members, past, present and future.

Mike Barrett, elected President of the django CMS Association for 2026 to 2028, thanks Mario Colombo and Joel Burch and sets out three priorities: a more valuable membership, an easier choice for agencies, and meeting in person at DjangoCon Europe.

Article

Hunting Down Quadratic Loops in django CMS

How PR #8913 removed quadratic work from django CMS menus, plugins, and page permissions: a permission-heavy menu on a 4,000-page site went from 11.7 seconds to 105 ms.

Article

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

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