LiveDocs Comments - coldfusion - 7 - htmldocs - 00000256.htm

coldfusion/7/htmldocs/00000256.htm

nicetim — 2006-07-27T10:33:40

Hi All,
This is a late post, but i have found another issue that dosnt seem to be on this page.

In normal HTML forms, if you submit the form, then refresh the action page, the form structure is reposted.
This is NOT true in flash forms. Be careful not to use form vars on the action pages of flash forms without first testing for their existance. This has caused me tons of problems and i dont understand why it dosnt work.

give it a try the next time you post a flash form.

tim

coldfusion/7/htmldocs/00000256.htm

clone45 — 2006-03-24T10:08:12

Be careful when using "_date" in the names of your input tags. Doing so can generate a "Form entries incomplete or invalid." error. Here's a small example to illustrate the problem:

This will throw an error.

coldfusion/7/htmldocs/00000256.htm

ASandstrom — 2005-12-19T10:55:30

Starting with the ColdFusion MX 7 Updater, Flash forms support the following:
- onFocus and onBlur events
- onLoad attribute, which means that you can run initialization ActionScript for the form

coldfusion/7/htmldocs/00000256.htm

Cheese_Man — 2005-11-18T14:05:31

I spent some time messing with the back/forward button flash forms issue ... "The form data has expired, please reload this page in your browser" ... I could not get the timeout parameter of CFFORM to work for me. In the end, I used someone else's idea of javascript to test for a cookie and then refresh the page if cookie found.
http://forums.devshed.com/t235953/s.html
(you need to add 'refreshPage();' to trigger the function)

coldfusion/7/htmldocs/00000256.htm

MARMC WebMaster — 2005-09-27T10:43:55

In working around bug 59602 (broken onsubmit functionality) mentioned on 2/17/05 (sthompson), 2/18/05 (halL), and 5/10/05 (doxx), I would caution against using the work-around suggested. The problem is that once the bug is fixed, the work-around will cause an infinite loop. This is because the onsubmit code is inserted into the body of _CF_checkCFForm_1, which will include a call to _CF_checkCFForm_1...

Where possible, use the onvalidate attribute in instead. If you need a general purpose validation block not associated to a specific element, you could try the following:

1) Add a javascript function like the following:

2) Add the following to the end of cfform:

3) Make sure to remove the onsubmit from .

Note: this does not interfere with any other elements that is marked as required. Those will still be validated as expected.

coldfusion/7/htmldocs/00000256.htm

dhoule — 2005-09-20T07:23:58

No screen name,

To have the Submit button submit the Flash form when the user presses the Enter key just do this...

type="submit"
name="submit"
value="Submit"
onkeyup="submitForm();">

Of course, the Flash form itself needs to have focus first, but if the user has been typing into the form it probably will.

coldfusion/7/htmldocs/00000256.htm

ASandstrom — 2005-08-15T10:02:46

Tip: You might want to take a look at the article "Advanced Flash Forms Techniques" here:
http://www.macromedia.com/devnet/coldfusion/articles/adv_flashforms.html

coldfusion/7/htmldocs/00000256.htm

jrunrandy — 2005-07-26T11:45:45

I just saw some cool Flash form discussions at http://www.asfusion.com/blog/. Check it out if you get a minute.

coldfusion/7/htmldocs/00000256.htm

FEW — 2005-05-30T09:33:19

It'ssimple to have multiple submit buttons and execute different
repsonsed based on which is pressed. Just add a different name
attribute to each button and test for it's existance in the response
page. If it exists, then that button was pressed and you can do what
you want for that user input.

i.e.

>
>

then, in the response page:

coldfusion/7/htmldocs/00000256.htm

doxx — 2005-05-10T04:36:04

Responding to the 2/18/05 comment from halL :

If your javascript function return a boolean value (true or false) your onSubmit attribute look like following statement:
...

because this attribute should return only one value...
...

coldfusion/7/htmldocs/00000256.htm

jrunrandy — 2005-03-07T10:12:13

This page neglects to mention that cfform height/width are required for flash forms, if they are used inside of a table. I have entered this into our bug tracking system as bug number 59900.

coldfusion/7/htmldocs/00000256.htm

davidsimms — 2005-03-03T08:04:35

Issue=clicking the Back button after submitting a Flash form causes the data submitting by the form to be lost. Setting the timeout attribute in the CFFORM tag to 60 doesn't help. Here's the code.

method="post"
action="action.cfm"
format="flash"
timeout="60">

Macromedia's documentation indicates that should all that is

coldfusion/7/htmldocs/00000256.htm

halL — 2005-02-18T10:32:12

Responding to the 2/17/05 comment from sthompson:

Both of the issues you raise are bugs.

The first issue, where you cannot use standard cfform validation if you specify an onSubmit attribute (bug number 59602), has the following workaround:
To enable standard cfform validation when you use an onSubmit attribute, add the following statement to the onSubmit attribute, replacing CFFORM_1 the value of name attribute of your form.

return _CF_checkCFFORM_1(this)

For example:

We have entered a bug (number 59844) for the change in behavior of the scrptSrc attribute, which now specifies a directory, not a file.

coldfusion/7/htmldocs/00000256.htm

sthompson — 2005-02-17T16:50:53

In MX 6.1, when you specify an onSubmit attribute in , ColdFusion calls the CF JavaScript validation, then calls the code you specified in the onSubmit attribute.

In MX 7, if you specify the onSubmit attribute, ColdFusion will only call the function you specify and not perform any cfform validation. This is a significant difference.

Further, the scriptSrc attribute in 6.1 pointed to a file. In 7, it points to a path. This essentially breaks any cfform code. I think it would have been better to add a scriptPath attribute, then deprecate scriptSrc.

coldfusion/7/htmldocs/00000256.htm

halL — 2005-02-17T08:44:57

In the cfform tag, you must end the background-color style definition with a semicolon (;), even if it is the only or last definition in a style attribute.

While, currently, this is the only case in Flash forms where the semicolon is always required, you should end all style definition with semicolons, even if they are the only or last definition in the style attribute.
For example, you should do the following:

And not the following: