Restore FK logic and best way to ignore fields about django-reversion HOT 3 OPEN

Hi @TonisPiip!

From the docs, the admin integration automatically follows some kinds of relation when auto-registering models:

If you’ve registered your models using reversion.register(), the admin class will use the configuration you specify there. Otherwise, the admin class will auto-register your model, following all inline model relations and parent superclasses. Customize the admin registration by overriding VersionAdmin.register().

Following a relation means that relation is always grouped into a a revision whenever the model is saved. Possibly this is what's causing your problems?

There's no current feature to ignore fields as part of the ignore_duplicates check. I'd be happy to take a PR for that feature, as it seems useful!

from django-reversion.

Thanks for the pointer for the doc, I do fear that is not the issues, or maybe I'm not understanding it well enough.

The modeladmin which has been registered has no inlines, just a 1on1 field. Is there any logic for restoring that when you restore, and the model as a (FK or 1to1) relation to another registered model, that model also gets restored?

from django-reversion.

Are you using manual @reversion.register() calls for your models?

from django-reversion.