1👍
✅
I would try enabling debug=True
and serving through foreman locally, or maybe even uploading this setting to heroku to see the stacktrace.
I don’t think the problem is on the JS side.
0👍
From the http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
500 Internal Server Error A generic error message, given when no more
specific message is suitable
This is a server error. From the JS side it’s completely legal response which can occure and you should be able to react to it (showing the message to the user that the communication to the server has failed, or any other action).
You must look for the error on the server side. There should be an error in the logs.
- [Answer]-OneToOneField QuerySet returning empty dict
- [Answer]-Jstools build – JavaScript causes problems after compilation
Source:stackexchange.com