-
8 Jun 2009 12:50 AM #1
[FIXED][3.0rc2] Retrying on an Ext.Direct form submit changes transaction type
[FIXED][3.0rc2] Retrying on an Ext.Direct form submit changes transaction type
Hey,
Here's a quick bug description:
Set a form to submit using an Ext.Direct call (api: {submit: ...})
The form sends the request to the server in the proper format (POST request). If the request gets a 404 response, it will retry, but the new request will no longer be a POST transaction but a regular Ajax one, losing the form values too.
Sample:
Initial request:
Retry:PHP Code:extAction Account
extMethod login
extTID 9
extType rpc
extUpload false
tbPassword kent
tbUsername gigi
PHP Code:{"action":"Account","method":"login","type":"rpc","tid":9}
-
8 Jun 2009 12:02 PM #2
Thanks for your report.
Description confirmed as of rev4257.
To reproduce this I took the examples/direct/direct-form example and loaded it up. Then I renamed the router.php to something else to create a fictitious 404 before hitting the 'submit' button.MJ
API Search || Ext 3: docs-demo-upgrade guide || User Extension Repository
Frequently Asked Questions: FAQs
Tutorial: Grid (php/mysql/json) , Application Design and Structure || Extensions: MetaGrid, MessageWindow
-
8 Jun 2009 10:53 PM #3
Thanks

-
9 Jun 2009 12:08 AM #4
I've just committed a fix, can you please test it out?
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
-
9 Jun 2009 3:20 AM #5
That worked for my test case. One reattempt was made after the first 404 and the transaction went out in same format.
MJ
API Search || Ext 3: docs-demo-upgrade guide || User Extension Repository
Frequently Asked Questions: FAQs
Tutorial: Grid (php/mysql/json) , Application Design and Structure || Extensions: MetaGrid, MessageWindow
-
9 Jun 2009 10:15 PM #6
I can't test it. Lacking SVN access

-
9 Jun 2009 10:18 PM #7
It's ok, MJ has tested it out. Marking this one as fixed.
Evan Trimboli
Sencha Developer
Twitter - @evantrimboli
Don't be afraid of the source code!
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote