-
Notifications
You must be signed in to change notification settings - Fork 407
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
Voting error responses are not rendering to the user #4548
Comments
I just checked my instance which is still running commit fde6e39 and it is doing the error responses just fine, i.e. both the Javascript is working and the response is also an HTTP 500, so it doesn't have anything to do with the HTTP code. I noticed this problem just recently within the last week, and there are only about a week of new commits since my instance which seems to confirm that. Commits comparison: fde6e39...1cef3bf Edit:Yeah, I just upgraded my instance to the latest version, and now it is experiencing the same error. |
Alright, I rebased the commits back and forth, and I was able to narrow down that it's commit 1760d1f which is causing the problem. With commit |
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
So it looks like this was done intentionally in jQuery 3.5.0. This means that we can no longer send Javascript responses for errors and expect them to evaluate. If we want this to still work as before, we'll have to change errors to use a 2xx HTTP status code for network calls on all Javascript endpoints. |
Closing because votes through the tag script function no longer error out. |
Neither the note popup nor the console message are appearing. Instead, the "Updating posts (X pending)..." just hangs there indefinitely. I checked and it's sending back the right Javascript, however that Javascript is not running. I'm wondering if it might be because the response is an HTTP 500 response.
Systems tested:
The text was updated successfully, but these errors were encountered: