Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
Fix compatibility with BitPay's upcoming API changes (May 1st 2018)
SHA512: a6160c1e9faef518faef5a60e3047cc2196e6ead2a5d6a8ac04878ec072f10655666b4aca1c5687828759e0524274f4307fffa02ed072e63c3bc0db03914aa47 bitpay-for-woocommerce.zip
- Removed non-working option to disable BitPay from the BitPay plugin config page
- Populate buyer email when creating BitPay invoice
- WC v3 compatibility fixes
- Change Mcrypt to OpenSSL (#77)
- Improve logging around updating order states
- Present error when mcrypt is not loaded
- It is suspected that certain filters are applied in the call stack of retrieving the order_total property on a WooCommerce order. These filters may return a string with non-numeric or decimal characters.
- If this is the case, dealing with an order_total is very problematic because we cannot know how to properly cast this string into a float in order to pass this value to BitPay via the api.
- To get around this issue, prior to setting the item on the BitPay invoice, we call WC_Cart's calculate_total, which is contracted to return a float. This method is reported to be available as of WooCommerce 2.1.0.
- ipn_callback will use the WooCommerce Order Numbering System filters for order searching in WooCommerce.
- Security issue with ajax calls
- New order status setting which also fixes issues with new orders being set to On-Hold and triggering emails