I discovered recently that when an existing member uses a ‘Buy Now’ Paypal button for a 12 month membership, it treats them as a new user, asking them to set up as a new user after making payment rather than just adding the 12 months to their existing EOT.
This previously worked fine when I originally set up and tested the buttons and now when I create a new button and test it (with a nominal 1p fee) it does the same as above. I have recently upgraded to S2member Pro but am still using the standard Paypal buttons.
It asks you to login? You mean it lets you create an account if you’re not logged in, right?
Buttons are still fine. And proration is not needed for buy-now, the new paid time is added to what the person had left.
Hi James.
Those members were most likely not logged in when they paid, so the payment went towards a new signup. You can have them signup a new account, so that their new signup links get used, but then edit their old account to update it with the new paid time and delete the duplicate account.
It’s important that the member is logged into his existing account when the page with the payment button is loaded, that way his account will be referenced and the new payment will go towards it, instead of a new signup. With buy-now, the new paid time is added after the existing EOT time for the user, extending his access.
I suggest that you put the renewal button in a page that only logged in users can access, like with s2Member Level 0 restriction, which is basically any logged in users. Or put it in the Login Welcome Page, that is not visible by visitors, only logged in users.
I thought that they may not have been logged in so tried with a test user account when I was definitely logged in and it still happened. I tried using the button short code and it works as it should but when I use the longer code (so I can add a T&C checkbox) it doesn’t! It all worked perfectly until recently. I did change server to a virtual server so would that make a difference??? Something to do with PHP?
I’m a real beginner so please excuse if I’m missing something obvious!
Thanks for your advice. I have decided to keep the shortcode for the button (which recognised an existing member fine) and just add a terms and conditions field to my registration form that must be checked rather than using custom coding.
I still don’t understand why my custom code stopped working but for now it’s sorted
