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.
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:
- Fixes the default value of the setting
CMS_INTERNAL_IPSto reflect the documented behaviour. - Implements numerous permission-related cleanups and fixes.
- 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
Article
Plugin Architecture Is Editor Experience
Lessons from building the component architecture behind the new django CMS website.
Article
Make Your Django Application Editable
The CMS doesn't need to own your data to make it editable.
Release
django CMS 5.0.11 and 5.1.2 released
Both are patch releases focused on security, stability, and compatibility. We recommend that users of the django CMS 5.0 and 5.1 series upgrade.