Re: [ic] payment only if every field is correct

[Mark Johnson <markj@redhat.com>]

You are right. One check is performed after the &fatal=yes. The rest are
ignored.

Javier Martin wrote:
> 
> Hello again,
> 
> I've found the solution in the "Advanced Multi-Level order pages" somewhere
> in the docs!  What was happening is that I was misplacing the &fatal=yes
> pragma in the order profile. The exact place where it should be is right
> before the last field of the customer data, for example
> 
> >>>>>>>>>>>>>>>>>>
> 
> fname=required
> lname=required
> address1=required
> country=required
> state=required
> 
> &fatal=yes    <-- abort if some error from now on
> 
> email=required  <-- now check the email
> email=email
> 
> &charge=custom authorizenet   <-- charge the customer
> 
> >>>>>>>>>>>>>>>>>>
> 
> It seems that it works because the &fatal=yes pragma tells interchange to
> abort the profile if any error occurs, but only after the following check is
> performed. If you put the &fatal=yes after the "email=email" check, then the
> custom charge routine is still executed although there have been errors in
> the earlier checks. Am I right?
> 
> Javier
> 
> > -----Original Message-----
> > From: interchange-users-admin@developer.akopia.com
> > [mailto:interchange-users-admin@developer.akopia.com]On Behalf Of Javier
> > Martin
> > Sent: lunes, 28 de mayo de 2001 18:37
> > To: interchange-users@developer.akopia.com
> > Subject: [ic] payment only if every field is correct
> >
> >
> > Hi,
> >
> > If you try buying something in the simple catalog that comes with
> > IC 4.6.5,
> > you'll see those red alerts showing when you miss some field. The same red
> > messages appear when some error occurs while validating the credit card
> > number, BUT you'll notice that no credit card validation takes
> > place unless
> > the user data fields are all filled in. However, I have written a new
> > catalog from scratch, and find out that the credit card
> > processing is donde
> > altogether with the validation of all the fields, so as a result, the
> > customer is charged every time he clicks "Submit" no matter the personal
> > data is valid or not.
> >
> > My question is: how does the simple catalog do to manage this? I can't
> > figure it out from the catalog files. I have examined the
> > profiles.order and
> > the ord/checkout.html without noticing anything different from my catalog.
> >
> > Javier
> >
> > _______________________________________________
> > Interchange-users mailing list
> > Interchange-users@lists.akopia.com
> > http://lists.akopia.com/mailman/listinfo/interchange-users
> 
> _______________________________________________
> Interchange-users mailing list
> Interchange-users@lists.akopia.com
> http://lists.akopia.com/mailman/listinfo/interchange-users

-- 
Mark Johnson
Senior Systems Architect - Professional Services
Red Hat, Inc.
E-Business Solutions
markj@redhat.com
703-456-2912