On Dec 1, 1:31 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > To not invent an artificial example could you describe your task in more > detail?
Sure, I have a long application form for a workshop (name, employment, resume, ... 65 fields). The user logs in to the site via django.contrib.auth.view.login, standard django fare. Then the user is allowed to apply for workshop xyz. If the user clicks save but does not complete the form, errors are shown and the user gets a message explaining the incomplete state of the form, but the form data is also saved in the database, just flagged with complete = 0. Only when the form validates does Application.complete field get set to 1 so reviewers know to look at it. This process allows the applicant to continue their application at a later time without completing the form. I'm currently doing this without AutomaticManipulator but I might have the need to override things later. Not sure yet. Originally I thought to use the same technique as in the RegistrationForm and write the manipulator, wrote my original mail, but it wasn't necessary just to skip validation. So I came up with this newbie approach. http://dpaste.com/3435/ One thing that worries me is, if skipping validation renders the data insecure? Since I haven't peeked much at the internals I'm not sure where string escaping and other types of form data checking takes place either. What other problems might I run into by disregarding manipulator.get_validation_errors and saving anyway? Thanks for you reply! --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
