Best strategy for integrating with django-reversion

Let’s say I have a model:

from parler.models import TranslatableModel, TranslatedFields
...

class House(TranslatableModel, models.Model):
    global_name = models.SlugField(max_length=255, db_index=True)
    translations = TranslatedFields(
        name=models.CharField(max_length=255),
        description=models.CharField(max_length=255, blank=True),
    )

Registering this model with Reversion is generally as easy as:

from reversion import VersionAdmin

class HouseAdmin(VersionAdmin):
    ...

This won’t follow fk or m2m relations by default, so I have added this to a common app:

reversion.register(HouseTranslation)

and this to the models.py described above:

reversion.register(House, follow=["translations"])

which doesn’t seem to restore properly. It is always displaying the most recent revision/versions no matter which historical revision you view. Via the command line, I can see that the correct data appears to be written to the revision, including a version for the parent model, and a version for the translated attributes model. Is this at all the correct way to do this, or is there some alternative method? I am looking into VersionAdapters to do this in a custom way, but want to see if there are simpler methods.

[vdboor]

It seems that Aldryn is actively using django-parler for multilingual support, and they have written a version adapter for it. It’s worth looking at, and if anyone would be able to port that into a module for parler, I’d be very happy!

See:

• https://github.com/aldryn/aldryn-reversion/blob/master/aldryn_reversion/admin.py
• https://github.com/aldryn/aldryn-reversion/blob/master/aldryn_reversion/core.py

[esistgut]

Thank you.