Release | April 3, 2014

django CMS 3.0 RC2 released!

Today we release django CMS 3.0 RC2

5 minutes read

Coincidentally this comes together with the 3000th ticket closed. People have thoroughly tested RC1 and we can report that we've fixed all the issues found.

One significant change since RC1 affects the static_placeholder templatetag. In RC1 static_placeholder was site-aware. We've changed this: static_placeholder is now once again not site-aware by default.

If you do need a site-aware static_placeholder follow these instructions:

  • change your templatetags to: {% static_placeholder "content" site %} (site doesn't need to be defined in the context)
  • Go to the static placeholder admin and change the static placeholder's new site setting accordingly.

Please test RC2 again!

Quick Upgrade Guide: http://docs.django-cms.org/en/develop/upgrade/3.0.html#upgrading-from-2-4

Full Upgrade Guide: http://docs.django-cms.org/en/develop/upgrade/3.0.html

Try out the new django CMS Installer (still beta):

djangocms-installer: https://github.com/nephila/djangocms-installer

$ pip install --upgrade virtualenv
$ virtualenv env
$ source env/bin/activate
(env) $ pip install djangocms-installer
(env) $ djangocms -p . my_demo

Go through the new tutorial:

https://github.com/divio/django-cms-tutorial/

Check Transifex to make sure your language is fully translated:

https://www.transifex.com/projects/p/django-cms/

django CMS 3.0 final

If we don't find any major bugs in the next week, we will head towards the final release.

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.