On 5/30/06, spacedman <[EMAIL PROTECTED]> wrote: > > Ground up would be my way of doing it. Lets break it down... > > You need an 'update' view that only shows the fields you want changing. > That means a custom manipulator that only mentions the fields you want > to modify. Protect this view by making sure the logged-in user is the > user mentioned in the URL (/edit/123 where 123 is the id in the User > model). > > Then write a template that shows the form that this manipulator is > controlling. > > As for the 'approval', well, add a field 'Approved' to your user data. > When the form is posted back, set it to False.
Just remember that the initial data will no longer be available for display until approval or if the admin wants to revert to it. Perhaps you will need two tables, one of approved data and one of unapproved data. Upon approval the data would be copied over the record in the approved table. That could get ugly though. > > Write another view only visible to Admin users that lists non-Approved > users, giving a link to the admin page for that user - then the Admin > can reset the Approved flag if the data is okay. > > Sketchy, but there's a few things going on here. > > > > > -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
