-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API browser not displaying POST form #3578
Comments
@nfletton it'd really help to have some steps to reproduce this. |
For example, if i have this ViewSet:
And send this request with Token Authorization from an external host:
request.data return:
But, if i send this request from a web form in the same host, with a started session.
request.data return:
But, request.POST is not empty:
If you need any further explanation, please let me know. 😃 Thanks! 👍 |
I'd suggest upgrading to 3.3.1 first and seeing if that resolves - if not then we'll consider looking into this further. |
Ok, it's solved 👍 Thanks a lot! |
Great! |
Can we leave this one open? For me, 3.3.1 does not solve the original problem I reported. I think the problem is that the POST form renders inside Bootstrap style tabs. In my scenario there's only one tab rendered by the template (tab-pane with id = post-generic-content-form) and as a consequence of the conditional code in base.html no Bootstrap tab markup is generated (i.e. the Nav tabs markup http://getbootstrap.com/javascript/#markup). Without the tab markup the code in default.js to activate a tab, has no effect. That JS code is: } else {
// If no tab selected, display rightmost tab.
$('.form-switcher a:first').tab('show');
} I'll take a further look but I have not seen what historical change is causing this for me. |
Closing this as #3600 was merged. |
There seems to be an issue with the display of the POST form in the 3.3.0 api browser and it's related to the switch to using bootstrap tab panes in the browser base template.
In 3.2.5:
In 3.3.0:
Adding an 'active' class to the tab-pane containing the POST form with DevTools results in the form displaying correctly.
The text was updated successfully, but these errors were encountered: