At 6/14/01 8:05 PM, Jeremy Anthony Kinsey wrote:
>Ok, using that psychology then, I suppose we would run out of money
>whenever someone just registers a domain. However, we do not. Why?
Because you've included some way to charge them for it in your local
script. People can't register new domains through manage.opensrs.net.
>Because we still have to approve of the registration before it goes
>through. So it would make sense that a renewal could work the same way,
>ie., the customer either renews, or adds years to their domain
>(submitting a CC of course)
Yes, that's my point. The customer needs to give you a credit card
number, but manage.opensrs.org is not set up for accepting credit card
numbers, displaying your renewal prices and policies, or any of the other
things you need to do for renewals.
So instead you unfortunately have to use a local script that does the
custom processing such as collecting money, then sends the request to
OpenSRS.
>and then we can just approve of it, assuming
>their CC/payment goes through. Again, this is the same thing we are
>doing now when it comes to a new registration. So why should a renewal
>be any different?
It's not. It's the same. In both cases there's a local script you modify
that collects credit card details, etc., and then sends the order to
OpenSRS.
Which script you should modify is debatable. As someone mentioned,
renew.cgi is easier to get started with, but many people have apparently
chosen to put the renewal functionality in manage.cgi because it presents
a more unified interface to the customer -- they just log in to manage
their domain and there's a renew link right there.
--
Robert L Mathews, Tiger Technologies
