Again, only in CF8 or above.

And wow, Nerida, yes, wonderful lady. She worked in the library of the 
government
agency I worked with in Australia back the mid-late 90's, which was the 
capstone to
the 15 years of my first IT career. Yep, I'm that old. :-)

 

/charlie

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
Rae
Buerckner
Sent: Tuesday, October 12, 2010 8:44 PM
To: [email protected]
Subject: Re: [cfaussie] Weird CFINPUT error

 

Hi Charlie,

Thanks :) I had figured that out, comes from having my head in Flex for so long 
and
suddenly switching back to straight CF.

Would it work as well for format="html"?

Cheers,

Rae

PS. I believe you know a very good friend of mine Nerida Hart?

On 13 October 2010 11:38, charlie arehart <[email protected]> wrote:

Rae: here's the simple answer: 

You need to say 'format="flash"' on your CFFORM, not 'type="flash".

Longer explanation: 

Well, if that worked in CF8, it was not working as a Flash datefield, but 
rather as an
HTML one. By having put in 'type="flash"' on the CFFORM to indicate a Flash 
form,
instead of 'format="flash"', CFFORM basically ignored it. 

In CF8, then, that would have let the CFINPUT type="datefield" worked because 
that was
added newly in CF 8 to be supported for HTML forms (again, you were not really 
doing a
Flash form). 

In CF7, though, that datefield option is ONLY supported for Flash forms. Since 
you
were not really doing one, the error is telling you that Datefield is not a 
valid
attribute value for Type. 

Actually, you should have gotten a more detailed error that would have (perhaps)
helped. It should have reported:

Attribute validation error for tag CFINPUT.

The value of the attribute TYPE, which is currently "datefield", must be one of 
the
values: TEXT,PASSWORD,HIDDEN,FILE,CHECKBOX,RADIO,BUTTON,SUBMIT,RESET,IMAGE.


I'm guessing that you are either only seeing the stacktrace (and not the error
message-though it shows the above even if "robust exception handling" is turned 
off)
or perhaps you're seeing this from a try/catch, and instead of seeing 
cfcatch.detail
you're seeing the output of cfcatch.stacktrace.

Hope that helps.

/charlie arehart
[email protected]
Providing CF and CFBuilder troubleshooting services 
at http://www.carehart.org/consulting

 

-- 
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en.

Reply via email to