Comments on: How to submit Ext forms the right way

By: pawel

pawel — Tue, 19 Apr 2011 20:05:35 +0000

Thank You!

By: Ross

Ross — Mon, 19 Jul 2010 20:15:02 +0000

After two hours of trying to write my own, yours worked in 10 minutes. I grovel before you…

By: Kumar McMillan

Kumar McMillan — Wed, 13 May 2009 00:10:04 +0000

You are a prince among thieves. Thank you for posting this code.

By: dhaas

dhaas — Thu, 29 Jan 2009 08:51:30 +0000

Yes I think this would be doable, but then you would not have a traditional form that gets submitted. Because forms cannot include sub-items that are not form-items.
But it would be surely possible to write a plugin that could be attached to any panel, and that recursively goes through all items and checks wether items are form-items and collects their data.
This data could then be transmitted over a custom request. You should then parse the answer of the “save” manually and show the user hints about fields that failed.
This whole thing would then not be a submit action anymore, but a plugin attachable to any panel, that would add a method getFormData() which would in turn collect the values of all fields in the panel.
- Certainly doable, but don’t copy to much code from this plugin, rather try to understand the code, and rewrite it from scratch for your needs.

By: SunWuKung

SunWuKung — Wed, 28 Jan 2009 13:54:03 +0000

Do you see any problems with using a recursive function to traverse the form? – go through all items, if it has items go through them as well

If you think that can work, we may give it a try – if I can convince my fellow here, since I can’t write code

By: dhaas

dhaas — Wed, 14 Jan 2009 18:18:35 +0000

@ SunWuKung:
This would not work out of the box. Unfortunately I see no easy way to implement that.
However Line 40-50 of the first code-block are the place to look at. It iterates over all items in the form. Maybe it would be possible to add an array of other forms / panels whose items should be collected into the options object of the submit method. But this could create problems when Ext is parsing the result of the request and tries to find the fields to display the errorText. Sorry, but I don’t know how Ext handles such more complex forms…

By: SunWuKung

SunWuKung — Wed, 14 Jan 2009 17:49:52 +0000

Would this work in cases when the submitted items aren’t direct items of the form – eg. they are in a fieldset, or inside a tab?
If not, how could this be extended to cases like that?

By: tonextone

tonextone — Thu, 24 Apr 2008 12:17:41 +0000

seems like you saved my life!
thanx!

By: dhaas

dhaas — Tue, 22 Apr 2008 07:10:32 +0000

@surfyogi:
standardSubmit is not compatible with OOSubmit because of the nature of OOSubmit.
The only way to get it to work would be, iterating over all fields in the submit method, getting their submitValue and setting that as value of the input-tag, and then submit the form the traditional way. This would however mean that values would be “flashing” prior to submit, because they would be changed.
And I even dont know, if it would work for comboboxes.

So sorry, OOSubmit has no solution for your particular problem, but could be the starting point for a custom solution.

The plugin does nothing more than overriding the standard submit() method of the form to use oosubmit instead of submit. Other than that it is the same. This is for example handy when some other code has to submit the form, but this other code does not know that it should use OOSubmit to submit the form. (For example third party code)

Hope that helps!

By: surfyogi

surfyogi — Mon, 21 Apr 2008 22:28:14 +0000

hiddenName works too, for combo values and STANDARD submit, instead of using OOSubmit:
items: [{ xtype:’selectbox’, id:’rt_air_class’,
valueField:’value’, displayField:’display’, hiddenName: ‘rt_air_class’, <<< HERE

By: surfyogi

surfyogi — Mon, 21 Apr 2008 19:39:26 +0000

Can’t figure out how to enable:

standardSubmit:true,

using OOSubmit. So far, it just gets ignored.

I also don’t understand the difference between using the plugin version vs not using the plugin version, or is there only one configuration for OOSubmit?

Seems like i need to modify the submit method to recognize this option, but every time I try, either I break OOSubmit and it no longer submits correct values, or the submit override is ignored and this option is never seen.

Could use a clue how to go about this, with a working example to examine.

thx, Jeff Papineau

By: luv2hike

luv2hike — Wed, 26 Mar 2008 12:45:30 +0000

Disregard my last post about the incorrect radio values being sent to the server. The Ext.ux.RadioGroup extension fixes this.

By: luv2hike

luv2hike — Tue, 25 Mar 2008 14:37:08 +0000

Overall I like this approach. However, it does not submit the correct values to the server for radio button groups. It sends true/false for the last button instead of the inputValue for the one that is selected.

By: Chris

Chris — Mon, 24 Mar 2008 20:55:10 +0000

Hi, thanks for this great extension.
Another fix you could include would be a workaround for the fact that you cannot currently have form fields named as arrays, ie foo[bar]. This currently throws an exception on submission!

By: dhaas

dhaas — Wed, 12 Mar 2008 12:13:47 +0000

I have now updated the post, and fixed/improved various parts of the code. Thanks for all the feedback!

By: dhaas

dhaas — Wed, 12 Mar 2008 11:04:29 +0000

Ah, now i see the problem. A fix is underway…

By: dhaas

dhaas — Wed, 12 Mar 2008 11:01:48 +0000

@Infinit: Sorry I do not see your problem. As the original submit action, i use the getMethod() call to retrieve the method to use. OOSubmit calls the original getMethod of the submit action so it should work exactly as the submit action.
Why do you use “_method” instead of “method” to specify the method? In my opinion this would never work, since getMethod() only looks at the following places to find the method:
this.options.method
this.form.method
this.form.el.dom.method

Is this perhaps a typo?

By: Infinit

Infinit — Wed, 12 Mar 2008 10:15:26 +0000

Error when used with a REST style rails backend => When I post a modified record, if configured params: { _method: ‘PUT’ } rails should recognize the request as PUT and route the request to a controller’s update method.
Can you fix this? ( the orignal submit method hv no such problem)

By: dhaas

dhaas — Sat, 08 Mar 2008 00:13:58 +0000

First: I apologize for not responding quickly. I’m currently moving at home and have not been able to get online for some days.
Thanks very much for your reponsens!
@kimu: You are right, i simply forgot that line when copying it out from my file, sorry! Also thanks for the improvements in the date getSubmitValue() function, i will incorporate that.
@Oleg: Yes it should read plugins: instead of plugin:. That was a typo.

Regarding the fileUpload problem: Yes you are right, thats a problem. Until now I simply did not have to deal with file uploads. But for file uploding, I would rather use one of the various file upload extensions floating around in the ext forum.

By: kimu

kimu — Fri, 07 Mar 2008 18:47:48 +0000

Another problem with this solution is that if fileUpload is set to true file aren’t uploaded