I am using Popup editing on several different grids in my application. When a user edits an existing record and saves the results, the data will commit/save properly, but the PopUp window will not close.
The method for the .Update method is called successfullly, the record is submitted succesfully to the database, and the server responds with a 200 response so everything is successful. However, the window remains open.
The response from the Update method is "return Json(ModelState.ToDataSourceResult());" exactly as I have seen in the demos. I have confirmed that the ModelState is valid.
This only happens on two or three grids that use PopUp editing. The remainder work properly.
Does the grid compare the return result to what is posted to verify success? Or, does it simply check for a 200 response?
ADDITIONAL NOTES:
This appears to be IIS-related. It works fine on my local dev environment using the VS Dev Server. When hosting in IIS 7.5, or IIS Express the problem shows up.
FOLLOW UP:
I have solved the problem by changing "return Json(ModelState.ToDataSourceResult());" to "Content(ModelState.ToString());". This changes the response content-type to "text/xml" instead of "application/json" which seems to resolve the issue.
The method for the .Update method is called successfullly, the record is submitted succesfully to the database, and the server responds with a 200 response so everything is successful. However, the window remains open.
The response from the Update method is "return Json(ModelState.ToDataSourceResult());" exactly as I have seen in the demos. I have confirmed that the ModelState is valid.
This only happens on two or three grids that use PopUp editing. The remainder work properly.
Does the grid compare the return result to what is posted to verify success? Or, does it simply check for a 200 response?
ADDITIONAL NOTES:
This appears to be IIS-related. It works fine on my local dev environment using the VS Dev Server. When hosting in IIS 7.5, or IIS Express the problem shows up.
FOLLOW UP:
I have solved the problem by changing "return Json(ModelState.ToDataSourceResult());" to "Content(ModelState.ToString());". This changes the response content-type to "text/xml" instead of "application/json" which seems to resolve the issue.