-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClickBank return error: Page Expired, Duplicate Return-Data #205
Comments
Oh, that is wonderful. I did not realize they did this. That must be new then. I will test this to confirm shortly. I'm loving CB less and less all the time. |
Moving this to the "Future Release" milestone. Assigning this to myself |
That's friendlier. Thanks! |
Hello jaswsinc. I am also getting the duplicate data error every time.Currently I am using 140603 version of S2 member and using Clickbank for payment. And getting this duplicate data error on clicking on the product link. May I know in which version of S2member this problem is resolved (as you said in your last comment ) so that I can update my plugin. Any kind of guidance will be appreciated. Thanks |
@Sohil007 This update is planned for an official release of s2Member late this week. We are shooting for tomorrow. You should get a notice in your WP Dashboard about the update. You can also monitor our changelog here if you'd like: http://www.s2member.com/changelog/ 📋 |
https://websharks.zendesk.com/agent/#/tickets/2967
@jaswsinc This comes up frequently. I understand that the problem is that the user was already returned right after checkout, but ClickBank sends the return URL in an email too, so sometimes the user clicks the link in the email and gets that error.
I know s2Member considers it a duplicate, but could it just add a log entry (if enabled) and simply not show an error, and instead take the person to the custom thank-you page if there is one, or the home page, or something that doesn't cause the user to contact the website worried about his purchase?
The text was updated successfully, but these errors were encountered: