2.3.6 release
Today we released django CMS 2.3.6 which addresses issues when installing django CMS.
Bugs fixed in 2.3.6:
- [1651](https://github.com/divio/django-cms/issues/1651): Fixed django CMS failing to install if Django is already installed in the environment.
- [1555](https://github.com/divio/django-cms/issues/1555) and [1620](https://github.com/divio/django-cms/issues/1620): Fixed various issues related to home page changes which may lead to broken paths (when using the now deprecated CMS_MODERATOR). Thanks to Ioan Alexandru Cucu for the fix.
As per usual, you can grab this release from pypi using pip.
Jonas Obrist
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.
Case Studies
How we built our professional services digital platform using django CMS
Compound Partners is a UK digital consultancy specialising in audience-centric user experience and content architecture for professional services firms. Fifteen years ago, a developer's recommendation pointed us at django CMS. Today, our entire business is built on it.