With the PayPal Pro forms, payment processing is done on-site, and the forms always look fine with the correct price shown. I’ve had new members sign up this morning with no issues. But every so often, maybe once every few months, someone will report getting the error message after clicking the payment button. Then they try again and it works.
S2 Button code suddenly not working with PayPal
Don’t know anything about Pro Forms. We don’t use anything that processes cards on site - being PCI compliant is pain in the arse. But at least they are working for you!
Things have gone quiet. Is this good or bad?
Christian emailed me earlier, We gave him admin access to a site that has the problem and is not in active use yet, but has a working PayPal IPN connection, so he can do what he needs to fix the problem and update the PayPal system for s2.
He can use it as much as he needs to in order to give us a more up to date PayPal system!
I am going to assume he is busy doing that. 
Sid
2 Likes
yep, working on it 
2 Likes
Making progress.
4 Likes
Noticed something had changed earlier this week, our PayPal button for subscription has been used for 2 years without change. Then now the customer is diverted to a standard checkout where the they have to enter an amount. The confirmation email has the payment going through. The recurring payment one is not received and the subscription is not included in the ‘Live Subscriptions’ of current subscribers.
I only include this as others with a simple integration can see the issue as above maybe the same as theirs.
I use Stripe Pro Form with the Standard PayPal button as an alternate payment on the page. I have removed this and hope #clavaque is able to fix.
Chris
Hi Chris.
PayPal changed the button encryption a week ago, and broke the PayPal Payments Standard buttons.
The solution for now is to deactivate button encryption in s2’s options, and allow unencrypted buttons in PayPal’s options. WP Admin > s2Member > PayPal Options > Account Details > Button Encyption
Try that and let me know if it helps.
changing the Encryption status for the button gets round the problem as you indicated #clavaque.
Look forward to this being fixed so we can ensure encryption is present going forward.
Thanks for this…Chris
1 Like
Any more progress on this?
1 Like
Some progress. 
Nothing to show for it yet, though. New gateway integrations are complex. 
2 Likes
Yeah, my CTO said pretty much the same thing. No idea why PayPal decided to make it more complicated!
Sid
1 Like
Are you still using s2Member with encryption turned off?
Yes. No choice - but also developing a plan to move to simple membership if we don’t get s2 working soon.
PayPal still has the issue with not letting users pay with their PayPal balance - it’s not related to the encryption thing - that PayPal told us they would fix. That hasn’t happened, but at least with encryption off people can pay with credit cards. They don’t know yet we had to turn off encryption off. I’d rather NOT have to tell them.
Sid
Sounds like other plugins avoid using encryption, and most people wouldn’t know what button encryption is anyway. It’s probably not a big deal.
1 Like
Simple Membership uses encryption - they already did what Christian is doing (I assume) and work with the latest approach PayPal wants. But you are correct - most of the others like Membership Pro etc. are not using encryption. A few never did.
Since technically all plugins on WordPress.org are “open source” The CTO considering using the Simple Membership PayPal code as guide to create our own code to work with s2, but our entire Dev team will be tied up with the300 Project - beyond full time - for the next 6 months. Just no one available to do that.
Sid
NEW WRINKLE Christian
While unencrypted button work, s2 DOES NOT - DOES NOT ALLOW REGISTRATION.
Every single site is getting an error like this:
We tested it with logs on, but no idea what the issue might be.
We ran the test on 12 of our sites. Same error everywhere.
I put the logs in a zip file for Christian
Sid
1 Like
Thanks for the logs.
Is this with the buttons created with the s2 shortcodes? Does it happen always or only some? Do you have older logs from before this behavior so I can compare the entries?
Yes, with s2 buttons’
Happens EVERY time EVERY site
Do Not have older logs, sorry:grinning:
Sid
Any progress?