Release | January 14, 2011

django CMS 2.1 Release Candidate 3 was just released.

The django CMS core team just released the third release candidate for version 2.1.

5 minutes read

Documentation: http://django-cms.rtfd.org Source: https://github.com/divio/django-cms/tree/2.1.0.rc3

Please report any issues you find with this release to our issue tracker at https://github.com/divio/django-cms/issues, thank you.

Unfortunately, the release candidate 2 had a nasty bug in it which would break our MPTT page tree when moderation is enabled and certain actions were performed on certain types of trees. This issue was now resolved, thanks to the amazing effort of Øyvind Saltvik.

There were also a couple of less serious bug fixes:

  • Issue 658, Invalid search fields on global page permission admin
  • Issue 648, Frontend-editing on/off toggle fails when the current URL contains an anchor.
  • Issue 642, Short description of CMS plugins fails when no actual plugin instance is available.
  • Issue 641, 'PageUserForm' object has no attribute 'permission_acessor'
  • Issue 639, get_page_from_request fails when not being called on an admin URL but not a CMS admin URL.
  • Countless documentation and testing improvements.

Please help testing this third release candidate and enjoy our django CMS.

In the name of the whole django CMS core developer team,

Jonas Obrist

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.