[ic] Orders to countries which have no states/provinces ?
Gert van der Spoel
gert at 3edge.com
Sun Nov 4 11:03:27 EST 2007
> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
> users-bounces at icdevgroup.org] On Behalf Of DB
> Sent: zondag 4 november 2007 17:43
> To: interchange-users at icdevgroup.org
> Subject: [ic] Orders to countries which have no states/provinces ?
>
> >> IC 5.4.2 with a modified foundation catalog. On my checkout form,
> >> "State/Province" is a required field. Some countries however have no
> >> entries in the State table. When customers try to submit orders
> >> shipping
> >> to such a country, a rather cryptic error appears and they can't
> >> proceed
> >> (I use Skipjack). The error appears to be coming from Skipjack, but
> I'm
> >> not certain that Interchange isn't generating the error. Error text
> is:
> >>
> >> (Payment process): There was an error accepting payment: Real-time
> >> charge failed. Reason: Length of customer state (-82)
> >> Credit Card Information: Length of customer state (-82)
> >>
> <snip>
>
> >
> > The error says 'length of state' to be an issue. Are you sure that
> 'NONE'
> > actually works?
> > I would assume that the state-length expected is 2 characters. So it
> would
> > be rejecting everything else.
> > If that is the case I'd add a <option VALUE='NA'>Not Applicable
> > as option ...
> >
> > CU,
> >
> > Gert
>
> Hi - NONE does work in my tests, and there are many examples in the
> State table of entries longer than 2 characters. Maybe 2 is a minimum
> but I'm not sure.
Gotcha. Checked a SkipJack manual (2004) and minimum requirement for state
is 1
(actually 1-40 is allowed).
So if you do not care about the State itself you could still go with the
<option value='NA'>Not Applicable setting. Then you do not need the
additional field.
You could put a test in your form profile in case someone from the US tries
to be funny and
Choose the 'NA' state ...
As SkipJack is requiring at least 1 character you apparently cannot make the
field optional.
CU,
Gert
More information about the interchange-users
mailing list