Tag release

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.

New packages of the django-fluent apps have been released.
These packages support the latest multilingual features (such as translatable SEO fields),
and Django 1.7 support is included for most apps.

The following package versions can be used in the requirements.txt for Django 1.7 support:

If you've used the previous beta versions, please note the upgrade notices. Some things had to be changed in a backwards-incompatible way for Django 1.7 support and multilingual support in SEO fields. See: https://github.com/edoburu/django-fluent-pages/blob/master/CHANGES.rst#upgrade-notices for all details.

Any dependencies will be installed automatically:

Note, the following packages are not checked yet for Django 1.7 support:

The project template has also been improved and updated:
https://github.com/edoburu/django-project-template/

To make creating multilingual websites easier, django-parler 1.0 has just been released! This package allows creating translatable user data, by translating Django model fields.

The release includes full documentation, and a few other awesome features:

• Python 3 support
• Caching translations for performance
• Prefetch support for performance
• Support translatable slugs
• Switch the language of the current page easily.
• Easy migration for projects that used django-hvad before.
• ORM methods for filtering translated models.

This is also the base for the next release of django-fluent-pages and django-fluent-contents, which also have multilingual support in git.

To make it easier for staff users to edit the current object in the admin, we've just released a new package: django-staff-toolbar. This allows displaying a nice menu at the website frontend:

The admin object is automatically detected, but can be overwritten in case the view doesn't provide an "object" variable in the template. See the README for more information