-
Notifications
You must be signed in to change notification settings - Fork 212
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
[ECP-9154][ECP-9491] Excessive network usage while making a virtual purchase #2581
Comments
Hello @embolden, Thank you for raising this issue. We've created an internal investigation ticket. Best regards, |
Hello @embolden, We've successfully reproduced this issue. But considering the current priorities, we won't be able to provide a fix soon. However, as a temporary solution, you can disable risk data collection which triggers all of those calls. Please add the following line to these configuration parameters.
You will be informed once we find an elegant solution to this issue. Best regards, |
Hello @candemiralp, We are also experiencing the same issue. While we know there is a temporary workaround by disabling the risk data collection, do you have any updates on when a permanent fix might be available? Especially given that Adyen v8 support/maintenance ends in January 2025 (https://github.com/Adyen/adyen-magento2?tab=readme-ov-file#support--maintenance). |
Describe the bug
When placing an order for a virtual product adyen.js makes ~100 calls to each of dfp.1.0.0.html, fingerprintjs2.js, and risk.1.0.0.js. This transfers 2.8MB over the network. Purchasing a physical product makes ~6 calls on the same environment.
To Reproduce
Steps to reproduce the behavior:
Assuming a clean Magento 2 installation with only the Adyen plugin installed and a sample virtual product.
Expected behavior
I would expect that 1 call would be sufficient for these.
Magento version
2.4.6-p4
Plugin version
9.3.0
Screenshots
Sorry for the resolution - Github limits to 10MB.
https://github.com/Adyen/adyen-magento2/assets/1679978/0a04b624-5149-45c8-90c6-7adaadbc84a7
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: