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

Follow up to #496 #557

Closed
angelleye opened this Issue Sep 18, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@angelleye
Owner

angelleye commented Sep 18, 2016

In #496 we made some adjustments that should be treating "Authorization" the same as "Sale" and set the Order to Processing so that inventory updates accordingly.

We have a user that's been waiting on this particular feature, but now they've updated to 1.2.4 and I have confirmed they have Authorization payment type set, but it's still leaving the orders in Pending status and not updating inventory.

https://www.angelleye.com/support/scp/tickets.php?id=652

Hi yes it is set to authorization. Authorizations are going through but again order is going to hold still instead of processing and inventory is not being reduced. This only impacts PayPal Express and started after the update before last. I also use Pay Flow and it still works flawlessly. Just Express has the issue.

@angelleye angelleye added this to the 1.2.5 milestone Sep 18, 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 may be related to #553 but I'm not sure.

Owner

angelleye commented Nov 2, 2016

This may be related to #553 but I'm not sure.

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Nov 23, 2016

Owner

I think the same guy from our ticket has now reached out to another plugin developer, who has now circled back to us asking for this same fix: https://mail.google.com/mail/u/0/#inbox/1588b5caa406ee0a

Owner

angelleye commented Nov 23, 2016

I think the same guy from our ticket has now reached out to another plugin developer, who has now circled back to us asking for this same fix: https://mail.google.com/mail/u/0/#inbox/1588b5caa406ee0a

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