Just renewed subscription and lost 24 days

Hi, my account was up for renewal in 24 days. Think 24 days calculates to renew date was 12/24/2017

I decided to renew today for another year. The system says my new renew date is 11/16/2018. Shouldn't it be 12/24/2018.I lost 24 days by renewing early.

Please fix.

Slightly related question since I haven't gotten an answer with my thread on credit card info updating...

I'm assuming you don't have "Auto Renew" turned on in your account, so did you have to enter all of your credit card info from scratch in order to renew?

This is something I'm trying to avoid having to do with Auto Renew.

Hi Mark - Your account has an additional 24 days - apologies for the delay.

Hi Glenn,

Thanks for getting back. I am looking and the site still has the wrong date. It should be 12/24/2018

but this is what I see

Not sure - I can look into it.

Admin panel shows 12/24/18

Glenn, what about the "Auto Renew" question I had in the other thread I started? Should I just turn it off and enter all my cCard info all over again?

Hi Tim - looks as though you renewed under v1 where we did not have auto-renew function so auto renew would not work for those that last renewed their subscription in v1. When we went to v2, we use Stripe and they provide us encrypted tokens so they store credit card information not us. So if renewing in v2 - auto renew will work for you, if last renewed in v1 - auto renew will not work for you.

Hi Tim - looks as though you renewed under v1 where we did not have auto-renew function so auto renew would not work for those that last renewed their subscription in v1. When we went to v2, we use Stripe and they provide us encrypted tokens so they store credit card information not us. So if renewing in v2 - auto renew will work for you, if last renewed in v1 - auto renew will not work for you.

Thanks, Glenn. I'll turn off Auto Renew and re-up on the day before my subscription expires. Hopefully re-entering the Ccard info will go smoothly.

Admin panel shows 12/24/18

That's interesting, Glenn. I just looked again and am still seeing

So my user info script may be accessing a different database file then your tool is accessing, and the file I am looking at is not being updated by the server from where the administration is changing it.

Well it looks there is still a bug in the system as it is 11/11/2018 regarding client displayed subscription renewal dates. My screen still says erroneously (from www.photo.net/my/settings/ ) my subscription renews 11//16/2018 and it should read 12/24/2018. I realize Glenn's admin database says 12/24/2018, but the database the client sees should tally the date 1 year from the current renew date, not one year from the credit card payment date. This should be corrected as a matter of good business practice and avoid be accused of deceptive practices. So what happens to me on 11/17/2018 - does my portfolio get wiped or just get inconvenienced and lose access to my premium features until I pay up early? Can you say with 100% certainty that the rest of Photo.net will remain functional on your database and not the database the client end is seeing? There should be no difference. I should not have to apologize for being persistent but this is obviously a bug and since the information conveys stated customer billed service time, it should be accurate and should be fixed to keep Photo.net on the up and up with good business practices. I have not been nagging you folks, it is going on one year since my last posting on this matter but as my erroneous subscription renewal date approaches I am getting a little concerned and I don't want to just renew early again and perpetuate the error another year. I realize you programers have had bigger fires to put out, but it has been a year, how hard is this to fix? You should be getting to this bug fix. Thanks.

Glenn's admin database says

It’s not Glenn’s database anymore. One of the moderators in another thread under Site Help recently announced Glenn is no longer with PN.

as a matter of good business practice

I’m sorry to say that if one were after good practices, they might want to avoid PN.

So what happens to me on 11/17/2018

I have a feeling you will know only when that date arrives.

Can you say with 100% certainty

For your sake, I hope that’s a rhetorical question! :rolleyes:

I should not have to apologize

And I hope you won’t even consider apologizing as you have nothing to apologize for.

being persistent

Probably won’t have an effect.

I am getting a little concerned

Many are concerned and there are many things to be concerned about.

how hard is this to fix?

i guess it depends on the fixer.

Best of luck.

It’s not Glenn’s database anymore. One of the moderators in another thread under Site Help recently announced Glenn is no longer with PN.

 

I’m sorry to say that if one were after good practices, they might want to avoid PN.

 

I have a feeling you will know only when that date arrives.

 

For your sake, I hope that’s a rhetorical question! :rolleyes:

 

And I hope you won’t even consider apologizing as you have nothing to apologize for.

 

Probably won’t have an effect.

 

Many are concerned and there are many things to be concerned about.

 

i guess it depends on the fixer.

 

Best of luck.

Hmmm, I don't know the turn over here. I remember when I used to write code, if I tried to work on code I wrote a couple months ago it might have just as well have been written by someone else. Of course in this case, it may have really been written by someone else. hopefully they use a lot of REMs or # to explain what each routine does.