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
Handle the related option in the main file woo-viet.php
Handle the compatibility for handle_onepay_ipn. It should be good. No need to change anything.
Handle the compatibility for handle_onepay_querydr
Check the case Woo Viet is just active
Check the case Woo Viet is upgradred
Improvements
Fixed this error:
[01-Sep-2020 16:36:41 UTC] PHP Deprecated: WC_Order::cancel_order is deprecated since version 3.0! Use WC_Order::update_status instead. in /app/public/wp-includes/functions.php on line 4773
Possible Improvements
Checked: vpc_Currency supports both VND and USD, or only VND? If both, it's a good idea to support for stores with the default currency = USD too. Result: tried to use USD but that does not help. However, I asked one of my friends directly. His company can charge foreign customers in USD directly. I guess this needs some kinds of arrangements between merchants and OnePay.
Docs: https://mtf.onepay.vn/developer/?page=modul_quocte
Diff between Domestic and International:
AgainLink
value is required in Int'l - while this is not required in Domestic.May apply for both?Yes, apply for both (tested)Different logo images
Different messages in $order_note
Plan to work on this
Solution 2: build two separated classes.Working branch: https://github.com/htdat/woo-viet/commits/add/onepay-intl
Check-list
handle_onepay_ipn
. It should be good. No need to change anything.handle_onepay_querydr
Improvements
Possible Improvements
vpc_Currency
supports both VND and USD, or only VND? If both, it's a good idea to support for stores with the default currency = USD too. Result: tried to use USD but that does not help. However, I asked one of my friends directly. His company can charge foreign customers in USD directly. I guess this needs some kinds of arrangements between merchants and OnePay.=> Moving this improvement idea to #76
The text was updated successfully, but these errors were encountered: