2.1.1. 2.3 release notes

2.1.1.1. What’s new in 2.3

2.1.1.1.1. Introducing Django 1.4 support, dropped support for Django 1.2

In django CMS 2.3 we dropped support for Django 1.2. Django 1.3.1 is now the minimum required Django version. Django CMS 2.3 also introduces Django 1.4 support.

2.1.1.1.2. Lazy page tree loading in admin

Thanks to the work by Andrew Schoen the page tree in the admin now loads lazily, significantly improving the performance of that view for large sites.

2.1.1.1.3. Toolbar isolation

The toolbar JavaScript dependencies should now be properly isolated and no longer pollute the global JavaScript namespace.

2.1.1.1.4. Plugin cancel button fixed

The cancel button in plugin change forms no longer saves the changes, but actually cancels.

2.1.1.1.5. Tests refactor

Tests can now be run using setup.py test or runtests.py (the latter should be done in a virtualenv with the proper dependencies installed).

Check runtests.py -h for options.

2.1.1.1.6. Moving text plugins to different placeholders no longer loses inline plugins

A serious bug where a text plugin with inline plugins would lose all the inline plugins when moved to a different placeholder has been fixed.

2.1.1.1.7. Minor improvements

  • The or clause in the placeholder tag now works correctly on non-cms pages.
  • The icon source URL for inline plugins for text plugins no longer gets double escaped.
  • PageSelectWidget correctly orders pages again.
  • Fixed the file plugin which was sometimes causing invalid HTML (unclosed span tag).
  • Migration ordering for plugins improved.
  • Internationalized strings in JavaScript now get escaped.

2.1.1.2. Backwards incompatible changes

2.1.1.2.1. New minimum requirements for dependencies

  • django-reversion must now be at version 1.6
  • django-sekizai must be at least at version 0.6.1
  • django-mptt version 0.5.1 or 0.5.2 is required

2.1.1.3. Pending deprecations

The CMS_FLAT_URLS setting is deprecated and will be removed in version 2.4. The moderation feature (CMS_MODERATOR = True) will be deprecated in 2.4 and replaced with a simpler way of handling unpublished changes.