In standard fusebox, you would set a fuseaction and post to your circuits
index.cfm. The fuseaction might be something like "validateform" and it
would switch case to do something like:
actions/act_validateform.cfm
if errors_count gt 0
displayers/dsp_myform.cfm
else
actions/act_saverecord.cfm
endif
(in pseudocode of course). There may be more that you need but that should
get you pointed in the right direction.
Mike Craig
-----Original Message-----
From: Peter Froh [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 4:01 PM
To: Fusebox
Subject: server side form validation
I am in the process of absorbing the Fusebox Methodology and I was wondering
how to handle server side form validation.
I tried to see how the "jazzloft" code did this in the shopping cart
curcuit, but it did not even use server side form validation, just client
side validation.
Do I need to submit the form to itself for validation and then use
cflocation to redirect user to a process fuse? How will that effect the
attributes scope? Will I not lose the attribute values from the form?
I tried sending the form to another process page, but when it failed the
validation and I had to redirect users back to the form, the attributes
scope lost the form information. So I tried session variables, it works but
all that locking, yuck!
There has to be a better way.
Any help would be appreciated.
Thanks.
Peter
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
