Someone posted a similar problem but I wasn't able to reproduce it. Would it be possible to post a standalone test case?

19 Jul 2013, 10:20 AM

jbender11

Sample app

Well, I spent an hour or so trying to put together a sample that shows the problem and of course the sample didn't have any problems at all. :( So apparently it is something a bit more subtle. It could be a timing issue or the fact that I upgraded the Architect app from a 4.1.1 runtime to a 4.2 runtime. The sample app was created initially as a 4.2 app in Architect so it didn't go through the upgrade process. Not really sure if that has anything to do with it at all.

I will spend some more time trying to recreate a simple app this weekend. But if I can't, I may have to include my entire rather large app.

John

23 Oct 2013, 2:46 AM

movys

I can confirm this error is due to prematurely closing the form panel. Upon submitting the form, either hide it (don't destroy it), or even better, destroy it in the success callback (this way you will be able to display potential validation errors from the server:

Pseudocode in your form controller:

Code:

// ... when submitting the form
var form; // get the reference to the form somehow - see the docs on your options
form.submit({
url: '/your/url/here',
success: function() {
form.up('window').close(); // this closes the window in which the form sits
}
});