On Friday, March 22, 2019 at 8:35:13 PM UTC+1, Raffaele Salmaso wrote: > > On Thu, Mar 21, 2019 at 2:42 PM Manlio Perillo <[email protected] > <javascript:>> wrote: > >> The view code is here: >> https://gist.github.com/perillo/2f828209cea84ff8c753f6f2524119f1 >> > I d >
Because I have remove every extra components. I removed all the middleware and all the other apps. However, as I said, this bug occurred original in the django admin app. I'm using the latest version of Django, and to make sure that the original source files have not been modified, I uninstalled and installed it again. The bug is still here. It may be a bug of Passenger (5.3.7), however I checked with a custom wsgi.py file and it sets the PATH_INFO correctly. This is my view: https://gist.github.com/perillo/fe4149fa610a52d090bb2062a9c83731 As i said at the start of the thread, if I comment the `{{ form }}` and uncomment the `<input type="file" name="xxx">`, Django works correctly. What I find strange is that it seems the problem is caused by my view (since only my view know the name of the form field), but my view *is not* called, and instead it seems (from the trace file) that the url resolver did not found a match for the request path. Thanks Manlio Perillo -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6fef4fca-2fab-4dd9-8180-f7009013d1b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
