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

Express Checkout - Invalid Token #337

Closed
angelleye opened this Issue Oct 20, 2015 · 9 comments

Comments

Projects
None yet
3 participants
@angelleye
Owner

angelleye commented Oct 20, 2015

We made some adjustments in #318 to try and handle this, but I think we missed something because I'm still getting reports of the problem.

Maybe we aren't checking for the session everywhere it needs to be..?? I know we're checking it before creating the SetExpressCheckout request, but are we also checking it prior to creating the GetExpressCheckoutDetails and DoExpressCheckoutPayment requests?

@angelleye angelleye added this to the 1.1.7.5 milestone Oct 20, 2015

@levansy2020

This comment has been minimized.

Show comment
Hide comment
@levansy2020

levansy2020 Oct 21, 2015

Collaborator

I have checked again but seems GetExpressCheckoutDetails and DoExpressCheckoutPayment have the condition to check Token is empty or not. Do you have any log or something else?

Collaborator

levansy2020 commented Oct 21, 2015

I have checked again but seems GetExpressCheckoutDetails and DoExpressCheckoutPayment have the condition to check Token is empty or not. Do you have any log or something else?

@angelleye angelleye removed the question label Oct 26, 2015

@angelleye angelleye modified the milestones: 1.2, 1.1.7.5 Oct 26, 2015

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Oct 30, 2015

Owner

Here is a ticket where this happened to a user recently. https://www.angelleye.com/support/scp/tickets.php?id=274

Owner

angelleye commented Oct 30, 2015

Here is a ticket where this happened to a user recently. https://www.angelleye.com/support/scp/tickets.php?id=274

levansy2020 added a commit that referenced this issue Oct 31, 2015

@levansy2020

This comment has been minimized.

Show comment
Hide comment
@levansy2020

levansy2020 Oct 31, 2015

Collaborator

a0e74ca remove debug code

Collaborator

levansy2020 commented Oct 31, 2015

a0e74ca remove debug code

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Nov 1, 2015

Owner

Looks like you've added more logic to try and catch when the token isn't available, but I'm curious why this is happening in the first place..?? It seems that the SEC and GECD calls are fine, but then for some reason the DECP request is not including a token.

Owner

angelleye commented Nov 1, 2015

Looks like you've added more logic to try and catch when the token isn't available, but I'm curious why this is happening in the first place..?? It seems that the SEC and GECD calls are fine, but then for some reason the DECP request is not including a token.

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Nov 1, 2015

Owner

Here's another ticket where somebody is getting invalid token: https://www.angelleye.com/support/scp/tickets.php?id=261

It's happening enough that I don't think it's simply a matter of sessions timing out. Somehow we're losing our data when building the DECP request.

Owner

angelleye commented Nov 1, 2015

Here's another ticket where somebody is getting invalid token: https://www.angelleye.com/support/scp/tickets.php?id=261

It's happening enough that I don't think it's simply a matter of sessions timing out. Somehow we're losing our data when building the DECP request.

@angelleye angelleye modified the milestones: 1.3, 1.2 Feb 29, 2016

@angelleye angelleye modified the milestones: 1.3.0, 1.2.5 Aug 16, 2016

@angelleye angelleye modified the milestones: 1.2.5, 1.3.0 Nov 2, 2016

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Nov 2, 2016

Owner

This seems to happen a lot from people on WPEngine because of their caching tools. If you contact WPEngine they are able to fix it.

I discussed this once with @kcppdevelopers and you seemed to think you might be able to disable caching of our stuff within the code to eliminate this problem.

Owner

angelleye commented Nov 2, 2016

This seems to happen a lot from people on WPEngine because of their caching tools. If you contact WPEngine they are able to fix it.

I discussed this once with @kcppdevelopers and you seemed to think you might be able to disable caching of our stuff within the code to eliminate this problem.

@angelleye angelleye modified the milestones: 1.3.0, 1.3.1 Nov 2, 2016

@kcppdevelopers kcppdevelopers modified the milestones: 1.4.0, 1.3.1 Dec 10, 2016

@kcppdevelopers kcppdevelopers self-assigned this Mar 8, 2017

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Apr 27, 2017

Owner

@kcppdevelopers You seemed to have an idea of how to address this when we discussed it before. Why did you mark it wontfix now?

Owner

angelleye commented Apr 27, 2017

@kcppdevelopers You seemed to have an idea of how to address this when we discussed it before. Why did you mark it wontfix now?

@kcppdevelopers

This comment has been minimized.

Show comment
Hide comment
@kcppdevelopers

kcppdevelopers Apr 28, 2017

Collaborator

I have try to find out solution to disable caching of our stuff within the code to eliminate this problem but WPEngine not allowed us using code.

Collaborator

kcppdevelopers commented Apr 28, 2017

I have try to find out solution to disable caching of our stuff within the code to eliminate this problem but WPEngine not allowed us using code.

@kcppdevelopers

This comment has been minimized.

Show comment
Hide comment
@kcppdevelopers

kcppdevelopers Apr 28, 2017

Collaborator

Now we have used woo session database table for store custom data, now everything is working fine.

Collaborator

kcppdevelopers commented Apr 28, 2017

Now we have used woo session database table for store custom data, now everything is working fine.

angelleye added a commit that referenced this issue Apr 28, 2017

@angelleye angelleye closed this Apr 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment