You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Hi everyone, i had a problem with the cancelation or abort payment step. I have a big database sylius with about more 400000 entries into 'sylius_payment' table. During the cancel process to get all payments, the retriving the id transaction paypal take so much time that cannot work proprely. That redirect me to the payment methods page without the 'cancelled' state or worst get an error 500 'OutofMemory' if you had limited in memory PHP. If i go to the payment methods page, i can't go re-attempt to validate an another transaction.
Steps to reproduce
Try to get more 10000 entries in 'sylius_payment' table
Go to the popin Paypal Checkout and click to 'Cancel and return to Test Store' or exit the popin to trigger the cancel state.
See the time between line 32 - 34 in PaymentProvider.php (too long)
Possible Solution
Create a new route, like create and complete route, with the orderid sylius
Pass this new route into PaypalButtonsController.php (line 139) with the orderid sylius
Modify CancelPaypalPaymentAction line 29 -31 to retrieve the order sylius and the last payment.
The text was updated successfully, but these errors were encountered:
SyliusPayPalPlugin version affected: master
Description
Hi everyone, i had a problem with the cancelation or abort payment step. I have a big database sylius with about more 400000 entries into 'sylius_payment' table. During the cancel process to get all payments, the retriving the id transaction paypal take so much time that cannot work proprely. That redirect me to the payment methods page without the 'cancelled' state or worst get an error 500 'OutofMemory' if you had limited in memory PHP. If i go to the payment methods page, i can't go re-attempt to validate an another transaction.
Steps to reproduce
Possible Solution
The text was updated successfully, but these errors were encountered: