I posted this to the dev-list, but I think there might be something
wrong with that list.  According to the Archives, not messages have been
posted to that list this month. So here it is again:

I browsed the archives and couldn't find anything on this. Forgive me if
this has already been covered.

I'm in the process of implementing reg_system.info.cgi, in order to
collect .info pre-registrations. Like many people, I've integrated
real-time credit card processing in-between the verify and thank you
pages.  One problem I'm finding is that much of the error checking
happens after the verify page.  Therefore, I'm afraid that people's
cards will be charged, but then when the order is submitted they may get
an error message that because their password isn't long enough, their
phone number format is invalid, or because someone else has already
pre-registered the domain through our account. It appears that when you
search for an "available" info domain, it only checks if the domain was
registered during sunrise.  If the domain was already pre-registered
through that RSP account, the domain will show up as available, until
they get to the thank you page, where they will receive a domain taken
error.  I for one am not looking forward to explaining to customers why
the domain shows up available at first, but then taken once they're
cards have been charged.

I've also noticed the following things:

- The passwords for .info domains must be 8 characters - unlike .coms.
Won't this create problems later? Will .info domains be able to be
transferred to existing profiles that have passwords less then 8
characters?

- I can't seem to get the "Use Profile Information from another .info
preregistration" form to work.  It works in the RWI, but not
reg_system.info.cgi. I get "Failed attempt: Authentication Error".

I'm imagining a support nightmare, with duplicate credit card
transactions caused by the error checking being done to late, and many
questions about why they got a "domain taken" error after filling out
the forms and charging their card. I may have the skills to modify the
scripts, but I'm afraid I just don't have the time or motivation.

ST

Reply via email to