All packages have been upgraded to support Django 1.7 and 1.8! Since Django 1.8 is a new long-term-support release, we’ve fast-tracked those releases to make the latest features available.

These features include:

• Multilingual support for all modules
• Multisite support for all modules
• Python 3 support!
• Improved caching for performance
• Additional SEO fields (e.g. page title)

For existing projects, you may want to upgrade to Django 1.7 only, until all other projects have migrated.
In our case, that is django-categories and django-contrib-comments.

New versions

Use the following versions in your requirements file:

Dependencies

Any requirements will be installed, but you can state these explicitly:

Note: upgrading from Django 1.6

Once you use Django 1.7, the included South migrations are ignored. Hence, when upgrading both Django and the CMS pacakges you need to upgrade the CMS modules first while keeping the project on Django 1.6. After deploying that on production (so migrations have been applied), you can remove South and upgrade the project to Django 1.7. The native Django migrations will be applied (faked in fact).

Note: Comments module on Django 1.7/1.8

In Django 1.7 and 1.8, comments module relies on the new django-contrib-comments module. This is not compatible with Django 1.8 yet, please help these guys create a new release! In the meantime, use the following requirement to have Django 1.7 support:

Support

Try it out, and let us know how it works!

Any issues can be posted in the GitHub issue trackers, posted at the django-fluent mailinglist or asked at #django-fluent on Freenode.