QuackFuzed.com is the personal ColdFusion coding blog of Matt Quackenbush. It exists primarily as a place for the author to learn, and hopefully to assist others in learning and/or avoiding some of the same pitfalls and mistakes. (Quack certainly makes enough mistakes daily to make up for the entire ColdFusion community.)
cfUniForm v3.2 - Bug Fixes and New Error Message Array Support
Posted on February 25, 2009 at 10:00 PM in Uni-Form Tag Library
Well, after several months of getting no love, cfUniForm has seen a flurry of activity in the last week. This evening I have released the latest and greatest, v3.2, which addresses a couple of bugs and adds a brand new enhancement.
Latest Articles
- No recent entries.
Eventually something really brilliant and witty will appear right here.
Categories
- ColdBox (21) [RSS]
- ColdFusion (92) [RSS]
- Fusebox (3) [RSS]
- General (22) [RSS]
- jQuery (15) [RSS]
- Kalendar (1) [RSS]
- Linux (1) [RSS]
- Mura CMS (1) [RSS]
- Railo (1) [RSS]
- Rants (5) [RSS]
- Transfer (8) [RSS]
- Uni-Form Tag Library (36) [RSS]



On 2/26/09 at 7:11 PM, Sana said:
Is it possible to add rule like this
<uform:field label="Email address"
name="Email"
type="text"
Rule="
{
required: true,
email: true
}
"
may be this is another enhancement requesst for uniform :)
On 2/26/09 at 7:16 PM, Matt Quackenbush said:
<uform:field label="Email Address"
name="Email"
type="text"
isRequired="true"
inputClass="email">
On 2/27/09 at 11:45 AM, Geoff said:
Not sure if you've fiddled with the illudium code generator thing, but it produces an array of structs for errors, something like this:
<cfif (NOT len(trim(getTitle())))>
<cfset thisError.field = "Title" />
<cfset thisError.type = "required" />
<cfset thisError.message = "Title is required" />
<cfset arrayAppend(errors,duplicate(thisError)) />
</cfif>
I don't think this is a de-facto standard for errors by any means, but for me, combining cfUniForm and the illudium generator for the quick generation of beans and forms for CRUD operations would be fantastic...
Any chance an error struct like that could be supported off the bat? (Yes, I could write something to change the keys of the struct, or change your code to accept a different error format, but it'd be nice to have something standardized if poss!)
On 2/27/09 at 4:39 PM, Matt Quackenbush said: