Clicking on "Pay now" corrects the entry, but the 'Active expiring' date becomes today's date, rhather than the original paypal payment/registration date. So a couple of questions, assuming a user first registered and paid on 09/09/12 and the correction with "Pay now" was made on 20/09/12; Also assuming that CB Subs is set to extend a renewal to the same date as registration, regardless of when payment is made:

1. How would this impact the anniversary renewal a year down the line? Do these mismatching renewal date entries need to now be corrected at table level to match the Paypal 09/09/13 recurring payment date? If so which table/column should be manually updated?

If table is not manually edited, will paypal simply take a payment on 09/09/13 and the account extend to 20/09/14? Or will there be issues?

What other issues do you envisage. I need to get these fixed soonest before we lose track of them. thanks, David

How is the bug fix going? At the moment this is causing alot of manual intervention setting user accounts to paid from within CB Profile, causing my clients some grief.

At present the CB Subs setup for this site is set to extend from the subscription date regardless of the actual payment date.

As you stated, having to re-enable the users manually as they are showing as having not paid, is pushing their registration renewal dates further back (i.e. extending anniversary as from the manual intervention date). It is still not clear to me whether issues will occur a year later when Paypal then renews on the original registration anniversary (as that is still lodged in the paypal profile), but their CB Subs subscription does not expire until a later period when an account was manually corrected.

I'm referring to your quote below. Why has this suddenly happened to the extent that EVERY NEW USER registering as a member is paying successfully in Paypal, and on the Users profile is disabled and saying Not Paid and with a PAY NOW Button?

You then go on to also say "The PDT was successful and the IPN informed you that the recurring signup was successful. So the users subscription should be working and active fine, but this will likely cause issues on renewal."

Yet you do not qualify what these issues on renewal will be or how they are to be resolved or avoided. Can you please provide a clear summary of your view of this whole topic, whether there are any bugs, display or otherwise, and what you propose to be done to resolve the problems my user is experiencing. If this is a configuration issue (what is it likely to be that it can cause a user ID by setting it to be zero??). That does not make sense to me.

krileon wrote: Have reviewed your install and tested locally. It seams for whatever reason the user_id isn't properly being pulled from the IPN. I've confirmed the IPNs are basically failing and only PDT is working. This is very likely an API change from PayPals end. I've created an immediate priority bug ticket for this to be reviewed and fixed immediately for a new release. I apologize for the inconvenience. For now please manually renew your users from within CB > User Management or edit their subscription from CBSubs > Subscriptions.

#3695