Thanks Matthew, but it looks like you're doing a data insert immediately upon a successful form validation. Am I seeing that correctly?
In my case, I have at several screens of form inputs from the user (customer login/info, shipping, payment, confirmation and possible more, depending on what is being purchased) one after the other, and I can't/don't want to insert the form entries after each page... I want to do it at the very end. Also, if validation fails, I want the failed form to appear with all previous user inputs included. Granted, I could stick the form inputs in Session or Client, but I don't like that, and I don't think that I should have to. I would think that passing the form entries as hidden form fields from step to step until completion is perfectly acceptable, if not most desirable, in a daisy chain of forms. The only drawback, if I do a cflocation anywhere in this process, I lose the form entries. If I'm thinking this wrong, please let me know. I'm just looking for a Fuseboxy way of doing server side form validation, without using cflocation. How are others doing server side, multi-form validation? Thanks, Jeremy -----Original Message----- From: Matthew W Jones [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 4:48 PM To: '[EMAIL PROTECTED]' Subject: RE: server side form validation?? There are many ways to handle this, here is what I like to do I have a fuseaction that is my form I have an xfa.submit that points to my processing fuseaction my processing fuseaction includes my validation if I have no errors I include my database work If I still have no errors, then I cflocate to my xfa.success If I have some errors from above, I do a cfmodule call to my xfa.failure, which is my form. This cfmodule call includes, among other things specific to me, attributecollection="#attributes#" fuseaction="#xfa.failure#" suppresslayouts="yes" voila' I have reloaded my form, passed my previously entered data, and it took me no extra time -----Original Message----- From: Jeremy Ridout [mailto:[EMAIL PROTECTED]] Sent: Monday, April 01, 2002 4:35 PM To: '[EMAIL PROTECTED]' Subject: server side form validation?? I'm writing my very first FB3 app, a shopping cart, and I'm working on the checkout forms. There are 4 stages that our customers must go through in order to checkout. Each of these phases, a customer must make several form inputs. My question is, what does the FB3 spec say about performing server side validation? I first thought about a separate fuse for validation and depending on the pass/fail result from the validator template, I would cflocate to the appropriate XFA. I quickly remembered why I don't like to cflocate for anything--I lost my form inputs no matter which direction I needed to go. The only obvious solution that I can see is a separate cfif at resides above the circuit switch (still within fbx_switch) that first looks to see if it should attempt to validate, and if so, depending on the result, modify the fuseaction to direct to request to the appropriate fuse... no cflocation necessary. It works very will and is only 3 lines of code. But, it sure doesn't feel like this solution is in the spirit of FuseBox. BTW, sorry if this topic has been beaten to death in the past, I tried to search the topica archives but it wasn't very useful. Thanks in advance, Jeremy ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
