Added: April/27/2006 at 11:40pm | IP Logged

Here is the scenario:

A user's account is going to expire in a few days, or has already expired. He pays the renewal and gets redirected to Register.asp where he can enter his username and pw to tell us which account to "unexpire". That part is already working. Now I need to actually change his expiration date in the system to one that is one year later.

add_new_account.asp will create a new account, but doesn't seem to have the ability to modify an existing one. Is that correct? Will I have to create that functionality myself? BTW, I know I can do it via the admin panel, but it needs to be automated - just between the user and the system.

Thanks in advance.

Added: April/27/2006 at 11:45pm | IP Logged

Yes, you will most likely have to update the database accordingly if you want it done through code though I gotta admit I am little confused at what your actually doing here.

He pays the renewal and gets redirected to Register.asp where he can enter his username and pw to tell us which account to "unexpire".

???? gets redirected to register.asp, why ??

regardless, there is probably nothing on the users side of things to do anything like what you are describing..

Added: April/27/2006 at 11:57pm | IP Logged

He gets redirected to register.asp so he can create an account. He has just paid through the e-commerce page and must now create his username and password. That is what happens for a new user. If he is a renewing user, he gets directed there also, but as explained above, the page is not quite equipped for that.

Does that make sense, or is that not how I should be doing it?

Added: April/28/2006 at 12:03am | IP Logged

If he is a renewing user, he gets directed there also

?? I dont get that.. why ? if he is a renewing user you should create some pages just for that.. not send them back to the register page.

if someone is paying for a membership IMO you should be letting them register for an account before they pay... so there would already be a username/password for them but you dont set them active until they pay... after they pay your payment code needs to go tell the system to make the user active..... thats the way to do it...

what exactly are you doing anyway ? Are you using one of my PayPal scenarios ? Are you trying to add your own payment gateway?

I just dont see how any of my default pay scenarios do what your describing and I am still confused at what your doing. If you are adding your own payment gateway you havent told me that and thats a pretty important detail.

Added: April/28/2006 at 12:19am | IP Logged

OK, I will create a separate renewal page. That makes sense.

I am not using PayPal; I have an e-commerce payment gateway set up. And it is not easy to interface with.

There are three scenarios that I have to handle:

1. User pays for an account right off - no free trial. First, he goes to the e-commerce page and pays. Then it redirects him to register.asp to create a username and password. In that case, what would be the benefit to doing it in reverse - creating a username/pw first, having him pay and then activating his account, as you suggested?

2. User signs up for a 30-day trial. He goes to register.asp and creates a username/pw. No e-commerce or payment involved.

3. User signs up for a 30-day trial. During or after that 30-day trial he wants to convert to a paid account. Or by the same token, maybe he already had a paid account and it has expired. Those are both the same situation - I must unexpire his account. That is the scenario I was describing in my original post. The first two scenarios are set up and working fine.

Does that make sense?