why not have two TextFields for the app, one for the approved content, and one for the edited and unapproved content?
Write a function that overwrites the content in the approved TextField with the item in the unapproved TextField and delete the unapproved TextField and tie that function to a select box. On Jan 15, 11:17 am, kaskado <[email protected]> wrote: > Hi, > not sure the subject said exactly what I want but I tried ;) I'm not a > web app/django expert so I hope you'll understand our problem. > > Let me first describe our system very quickly : > -On one side we have customers publishing content (text + images) > -On the other side, consumers, seeing and using this content > > When a customer publishes content, we want to approve it before the > content goes live to Users > > Until there... fine ;) > > However, when content has already been published, the customer can > still modify it. When a customer make a modification, we want to > approve that before the modification goes live. > > I wonder how are we supposed to treat that : > - Do we store the edited data separately until it is approved ? (we > want the customer to see his non-approved edited data in his view, > while the consumer sees the approved data) > - Do we use 2 databases, like one would use 2 branch codes with > release and development.. > > Help would be much appreciated. > Regards, > Jonathan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
