Django CMS Changelog

What's new in Django CMS 3.1.0

Apr 21, 2015

Remove django-mptt in favor of django-treebeard
Remove compatibility with Django 1.4 / 1.5
General code cleanup
Simplify loading of view restrictions in the menu
South is not marked as optional; to use south on Django 1.6 install django-cms[south]
Add system_plugin attribute to CMSPluginBase that allow the plugin to override any configured restriction
Change placeholder language fallback default to True
Remove plugin table naming compatibility layer
Remove deprecated cms.context_processors.media context processor
Add templatetag render_plugin_block
Add templatetag render_model_add_block
Add "Structure mode" permission

New in Django CMS 3.0.13 (Apr 16, 2015)

New in Django CMS 3.1.0 RC 1 (Apr 14, 2015)

New in Django CMS 3.1.0 Beta 1 (Mar 27, 2015)

Switch from MPTT to MP:
Since django CMS 2.0 we have relied on MPTT (Modified Preorder Tree Traversal) for efficiently handling tree structures in the database.
In 3.1, Django MPTT has been replaced by django-treebeard, to improve performance and reliability.
Over the years MPTT has proved not to be fast enough for big tree operations (>1000 pages); tree corruption, because of transactional errors, has also been a problem.
django-treebeard uses MP (Materialized Path). MP is more efficient and has more error resistance then MPTT. It should make working with and using django CMS better - faster and reliable.
Other than this, end users should not notice any changes.
Action required:
Run manage.py cms fix-mptt before you upgrade.
Developers who use django CMS will need to run the schema and data migrations that are part of this release. Developers of third-party applications that relied on the Django MPTT that shipped with django CMS are advised to update their own applications so that they install it independently.
Dropped support for Django 1.4 and 1.5:
Starting from version 3.1, django CMS runs on Django 1.6 and 1.7.
Action required:
If you’re still on an earlier version, you will need to install a newer one, and make sure that your third-party applications are also up-to-date with it before attempting to upgrade django CMS.
South is now an optional dependency:
As Django South is now required for Django 1.6 only, it’s marked as an optional dependency.
Action required:
To install South along with django CMS use pip install django-cms[south].
Migrations moved:
Migrations directories have been renamed to conform to the new standard layout:
Django 1.7 migrations: in the default cms/migrations and menus/migrations directories
South migrations: in the cms/south_migrations and menus/south_migrations directories
Action required:
South 1.0.2 or newer is required to handle the new layout correctly, so make sure you have that installed.
If you are upgrading from django CMS 3.0.x running on Django 1.7 you need to remove the old migration path from MIGRATION_MODULES settings.
Structure mode permission:
A new *Can use Structure mode* permission has been added.
Without this permission, a non-superuser will no longer have access to structure mode. This makes possible a more strict workflow, in which certain users are abnle to edit content but not structure.
This change includes a data migration that adds the new permission to any staff user or group with cms.change_page permission.
Action required:
You may need to adjust these permissions once you have completed migrating your database.
Note that if you have existing users in your database, but are installing django CMS and running its migrations for the first time, you will need to grant them these permissions - they will not acquire them automatically.
Simplified loading of view restrictions in the menu:
The system that loads page view restrictions into the menu has been improved, simplifying the queries that are generated, in order to make it faster.
Toolbar API extension:
The toolbar API has been extended to permit more powerful use of it in future development, including the use of “clipboard-like” items.
For an example of how this can be used, see the new Blueprint application.
Per-namespace apphook configuration:
django CMS provides a new API to define namespaced Apphook configurations.
Aldryn Apphook Config has been created and released as a standard implementation to take advantage of this, but other implementations can be developed.
Improvements to the toolbar user interface:
Some minor changes have been implemented to improve the toolbar user interface.
New templatetags:
render_model_add_block
The family of render_model templatetags that allow Django developers to make any Django model editable in the frontend has been extended with render_model_add_block, which can offer arbitrary markup as the Edit icon (rather than just an image as previously).
render_plugin_block
Some user interfaces have some plugins hidden from display in edit/preview mode. render_plugin_block provides a way to expose them for editing, and also more generally provides an alternative means of triggering a plugin’s change form.

Django CMS Changelog

What's new in Django CMS 3.1.0

New in Django CMS 3.0.13 (Apr 16, 2015)

New in Django CMS 3.1.0 RC 1 (Apr 14, 2015)

New in Django CMS 3.1.0 Beta 1 (Mar 27, 2015)

New in Django CMS 3.0.10 (Feb 16, 2015)

New in Django CMS 3.0.9 (Jan 13, 2015)

New in Django CMS 3.0.8 (Jan 13, 2015)

New in Django CMS 3.0.7 (Jan 13, 2015)

New in Django CMS 3.0.6 (Oct 8, 2014)

New in Django CMS 3.0.5 (Aug 21, 2014)

New in Django CMS 3.0.4 (Aug 16, 2014)

New in Django CMS 3.0.3 (Aug 16, 2014)

New in Django CMS 3.0.2 (May 21, 2014)

New in Django CMS 3.0.1 (May 1, 2014)

New in Django CMS 3.0.0 (Apr 15, 2014)

New in Django CMS 3.0.0 Beta 2 (Oct 19, 2013)