You could use contrib.contenttypes framework to do this pretty easily
provided the models you will be working with have a similar structure;
they all have a field called 'content' for example that would be
editable.
You can have a model that is the intermediate which has a generic
foreign key which points to the object which was edited. So when
someone edits an item , the data in request.POST is used to make a new
intermediate item rather than update the item that was actually
edited.
Then a moderator can decide to apply the update or not
This would also create a history of edits on each object and make
revision control and reverting rather easy.
This means the intermediate model is really the 'Heavy Lifter' of the
setup.
On Feb 14, 10:36 pm, iliveinapark <iliveinap...@brentonannan.com>
wrote:
> Thanks very much, Bruno, this is a pretty simple way of doing what I
> want.
>
> Now I just have to figure out to apply it generically over multiple
> levels of inheritance =/
>
> Cheers mate.
>
> On Feb 12, 10:00 pm, bruno desthuilliers
>
> <bruno.desthuilli...@gmail.com> wrote:
> > On Feb 12, 11:24 am, bruno desthuilliers<bruno.desthuilli...@gmail.com>
> > wrote:
>
> > (snip)
>
> > oops, forgot to actually use the custom manager:
>
> > > class MyModelRevision(models.Model):
>
> > (snip)
> > objects = MyModelRevisionManager()
>
> > > class Meta:
> > > unique_together = (('MyModel', 'published'),)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
