You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a backend returns a status code other than 200, then the response body is split on newlines and dumped into the form. This is problematic if the backend is returning a json data structure, since it will be dumped into the page unparsed.
Right now the only options are to change the backend to return plain text, or to return a 200 and then use a custom success handler.
Altering the backend for a single plugin, is not a particularly attractive choice. It would be better if there was support for a custom error callback that worked just like the custom success callback, but was used when the backend returned an error code.
The text was updated successfully, but these errors were encountered:
If a backend returns a status code other than 200, then the response body is split on newlines and dumped into the form. This is problematic if the backend is returning a json data structure, since it will be dumped into the page unparsed.
See: http://jsfiddle.net/xBB5x/1045/
Right now the only options are to change the backend to return plain text, or to return a 200 and then use a custom success handler.
Altering the backend for a single plugin, is not a particularly attractive choice. It would be better if there was support for a custom error callback that worked just like the custom success callback, but was used when the backend returned an error code.
The text was updated successfully, but these errors were encountered: