#23552: Bad request (Error 400) on almost all inline adding calls
--------------------------+------------------------------------------------
Reporter: nux17 | Owner: nobody
Type: Bug | Status: new
Component: HTTP | Version: 1.7
handling | Keywords: inline, error, http, response, 400
Severity: Release | Has patch: 0
blocker | UI/UX: 0
Triage Stage: |
Unreviewed |
Easy pickings: 0 |
--------------------------+------------------------------------------------
Hello,
I'm forwarding my Django setup to 1.7 and having a check for
incompatibilites/bugs from my setup previously on 1.6.
Working on a test setup, I found out most of the adding inline (green
crosses) models now retrieve a "Bad Request (400)" error. The URL seems to
have changed from 1.6, but this seems to work with some inline calls
(found one working and actually displaying the adding form).
Nothing on logs from Django, and Debug is set to True.
Cutting the URL from the slash '/' after 'add' just before the GET
arguments (to_field=xxx&popup=1) brings the page up.
This is blocking my deployment, and after being investigating about this
bug for half a day now I can't manage to find fix/info about it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23552>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.4bc681c441e0aedd2cc957545a743491%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
