Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
quote:
Originally posted by: Newsgroup User
@ AlwaysWannaLearn:
rtfm:
using <form> tag will submit to the form to the main page
using <cfform> tag will submit the form to the ajax ui control the form
is displayed in
Azadi Saryev
Sabai-dee.com
http://www.sabai-dee.com/
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I know this is an old post but I'm working with cfwindows in CF11, and I may have just figured out the problem. After 9 years, I imagine it won't help the original poster, but what the hey.
In my project, I have two CFWindows that allow the user to select the series of checkboxes and associate the records to two different data points. So let's say I'm working with widgets that can go either into product A or product B.
If the user comes to the page and opens the cfwindow "Widgets in Product A", they make their selections, save, and all is good. Likewise, if they come to the page and open the cfwindow "Widgets in Product B" and save, again, all is good.
But if the user comes to the page, opens A and then opens B, things break. On saving, B sees not only the widgets selected in current cfwindows, but also in previous cfwindow.
Thought I was losing my mind, but the conclusion I came to was that A CFWINDOWS'S HTML REMAINS IN THE DOM AFTER THE WINDOW IS CLOSED. Perhaps not news to everyone, but it was to me.
My guess is the original problem lay in using the same id name for a field in both windows causing the JavaScript to use an unintentional value. Making the var names unique worked for me. Hope this helps.
Regards,
Jeff Wogan