When using a regular HTML form, we rely on the browser to act like a regular 
browser.  Only the 'activated' elements of a form are sent.  Form elements with 
the same name and are 'activated' will be received by the server as a 
comma-delimited list.

In a regular form, only the button that is pressed is 'activated' so your 
scenario works correctly.

Now enter into the world of cfwindow/cfform.  These two tag-groups are 
extremely powerful, but do cause some changes in the way the form is processed.

As you mentioned, when you changed your cfform to a regular form, it worked 
correctly, but you lost the 'keep in the cfwindow' functionality.

Cfform and cfwindow appears to work together to submit forms via AJAX.  The 
script probably compiles the form in the usual manner, any field with an active 
value are sent to the server.  The ajax probably identifies the button that was 
pressed, by its name, and then gathers the values for that 'named field'

In this case, you can achieve your needs in 1 of 2 ways (probably a lot more, 
but working on little sleep here).

1.  make your buttons unique names, and parse on the server side based on the 
button that was pressed.
2.  create an additional hidden field, when one of the buttons is pressed, pass 
the value of the pressed button to the hidden field using javascript, and have 
your server check the value of the hidden field, instead of the button.


Hope this helps,

William

----------
William E. Seiter


On Apr 29, 2010, John Pullam <[email protected]> wrote: 


Thanx for all the feedback. I'm about 95% sure that I've done all this before 
and made it work. And the examples given have been tried too. There must be 
something different in my case. This simple use of 2 buttons on a page worked 
for me. But when I put it back into the live case it fails, so I think I am 
missing something there. 

I have trimmed out irrelevant code in an attempt to get this down to a basic 
test but still it fails showing me a string that has both button names (it 
didn't do this when I started with a single page). My case includes a cfwindow, 
so there are 2 bits of code below ... the page and the window.

The calling page: ...


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Want to reach the ColdFusion community with something they want? Let them know 
on the House of Fusion mailing lists
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:333244
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to