We are working on a django site in which we want to give users control over the content, but we want user users to have moderate content and the accepted content queue in case some superusers want to roll back data for a specific version in the past.
I cannot find a django application to do both things . I read about django-moderation and django-reversion, and I was wondering if there was a way to get them to work together.
I saw that this is a repeating question, but no one answers . The typical answer is this or that, but no one seems to have a solution to the problem.
I read that the main problem is that if there is moderation and versions for the content, it can (accurately) create a version tree .
But then I thought that I want to save only the accepted versions, then previous versions will generate lineal history back in time, that is, if I return something and accept a new thing, then I think it’s normal to remove the rejected branch from the point, where I returned when I accept (then save) the new version , which leads to a new branch.
Is this possible with django-moderation and django-reversion?
Application Information:
[1] https://github.com/etianen/django-reversion/wiki
[2] https://github.com/dominno/django-moderation