Afterpay

Hi Lisa,

Thanks for creating the ticket, and providing the reference number. A member of the support team will be in touch with you shortly.

Thank you.

Hi colourcascadefabrics,

Thanks for reporting this behaviour. Our engineers are now aware of this and are working to identify the cause. This is the first time this particular behaviour has been reported.

If this can be addressed from within the Afterpay Gateway for WooCommerce plugin, an update may be released in future. Any such update will become available through the standard plugin manager in the WordPress admin.

If you would like to request a member of the support team to assist in troubleshooting this individual case, please create a support ticket here:
https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406

Thank you.

Hi baebabebeauty,

Thanks for reporting this behaviour. The described conflict with the WooCommerce Product Add-Ons plugin has been reported, and a resolution has been developed already. This compatibility improvement will likely be included with the next official release of the Afterpay Gateway for WooCommerce plugin. If you would like early access to install a beta version of the plugin, please create a support ticket here:
https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406

Thank you.

Hi rainsey,

Thank you for reporting this behaviour. This has been relayed to the development team and release manager for review and consideration in future plugin releases.

As soon as a change has been verified and committed to a future release, it will become available for update through the standard plugin manager in the WordPress admin.

For the time being, please consider attaching a method to one of the following hooks, which are used by the plugin prior to rendering the HTML on the category pages and individual product pages:

• Filter: ‘afterpay_is_product_supported’ (Passes arguments: WC_Product $product; expects a Boolean return value)
• Filter: ‘afterpay_html_on_product_thumbnails’ (Passes arguments: WC_Product $product, float $price; expects a String return value)
• Filter: ‘afterpay_html_on_individual_product_pages’ (Passes arguments: WC_Product $product, float $price; expects a String return value)

Alternatively, to detach the Afterpay methods from the WooCommerce hooks entirely, perhaps based on some conditional logic, please consider the following:

remove_action( 'woocommerce_after_shop_loop_item_title', array(WC_Gateway_Afterpay::getInstance(), 'print_info_for_listed_products'), 15, 0 );
remove_action( 'woocommerce_single_product_summary', array(WC_Gateway_Afterpay::getInstance(), 'print_info_for_product_detail_page'), 15, 0 );

Thank you.