Re: Django & mod_wsgi, multipart/form-data forms, and hell

On Thursday 10 September 2009 10:45:01 Benjamin Kreeger wrote: > Okay, I just made myself think, which is dangerous. When I removed the > @login_required decorator from the view that handles the POST data, it > worked. > > But I'd really like the form to require the user to be logged in (as > part

Re: Django & mod_wsgi, multipart/form-data forms, and hell

Okay, I just made myself think, which is dangerous. When I removed the @login_required decorator from the view that handles the POST data, it worked. But I'd really like the form to require the user to be logged in (as part of the form brings up information about the user from request.user). On

Re: Django & mod_wsgi, multipart/form-data forms, and hell

And for what it's worth, the view asks for authentication using a @login_required decorator (and django.contrib.auth), and that's all hunky-dory, too. Haven't had any problems with that part of it before. --~--~-~--~~~---~--~~ You received this message because you a

Django & mod_wsgi, multipart/form-data forms, and hell

I've got a model that has an ImageField, and a ModelForm that uses this model. I've got my template set up using the form fields, and my form tag is set up with enctype="multipart/form-data" so the picture upload works. When I use the included Django development server (runserver command), I can