Afterpay

Hi @tinshapes,

Thanks for your message, and for the subsequent update. Great to know that you were able to address this challenge directly from within the WordPress admin.

Despite this particular instance already being resolved, it’s still possible that there is room for improvement – with regard to this challenge – from the plugin perspective as well. Further investigation has been scheduled to this effect. Preliminary findings suggest that it could be appropriate to replace uses of the WP_PLUGIN_URL constant with a call to the plugins_url method.

As always, any subsequent updates to the Afterpay Gateway for WooCommerce plugin will be distributed via the official WordPress Plugin Directory.

Thank you.

Hi @da_mask,

Thank you for your message.

The behaviour described here represents a known challenge that is expected to be addressed in the next release. In the meantime, please consider using the afterpay_html_on_individual_product_pages hook to hide the Afterpay content for either a specified array of Product IDs, or any instance of the “available between” message.

For example, the following code sample can be added to the active theme’s functions.php file:

/**
 * @param string     $str_html
 * @param WC_Product $product
 * @param float      $price
 */
function afterpay_hoipp_callback( $str_html, $product, $price ) {
    # Hide the "Installments by Afterpay available between X - Y" message
    if (preg_match('/available between/m', $str_html)) {
        $str_html = '';
    }
    return $str_html;
}
add_filter( 'afterpay_html_on_individual_product_pages', 'afterpay_hoipp_callback', 10, 3 );

Thank you.

Hi @embercide,

Thanks for reporting this PHP notice. The development team will investigate alternatives to the serialisation of the WC_Checkout object. In the meantime, please consider configuring the error reporting level of any Production environment to exclude notices.

Thank you.

Hi @embercide, @antonynz and @herman123456,

Please be advised that the latest release of the Afterpay Gateway for WooCommerce plugin (v2.1.0) includes several revisions to the checkout functionality for WooCommerce 3.6 and 3.7. Please reply to this topic if any verbose notices similar to those reported above are occurring in v2.1.0.

Thank you.

Hi @galapogos01,

Thank you for your additional question. Timelines for future releases are not announced to the public at this time. Official plugin releases are distributed via the official WordPress plugins directory.

Thank you.

Hi @boutiquelife,

Thank you for this suggestion, Stuart.

Please note that the rich text editors within the plugin settings page allow admins to customise the display of the Afterpay elements to suit the presentation needs of the individual WooCommerce store. These text blocks are stored in the WordPress database and are not modified or affected in any way during the plugin update process. This content can be filtered from the theme’s functions.php file, and each area has a different hook.

The checkout content does not have a rich text area for accepting custom base content. However, the Afterpay content that appears at the checkout can be filtered by attaching a method to the afterpay_html_at_checkout filter hook. This can be done from the theme’s functions.php file, which will not be altered during the plugin update process.

Happy to discuss further if the response above does not address the specific challenges experienced.

To ensure the Afterpay Merchant Services Team are able to provide tracking for enhancement requests submitted by partnered agencies and merchants, the team recommend submitting all support requests via the following web form:

• https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406

Once submitted, the requester will be provided with a tracking number and a dedicated support team member who will be in a position to provide individualised assistance.

Thank you.

Hi @joelseneque,

Thank you for your message.

There is currently a known compatibility challenge relating to custom checkout fields. This is planned to be resolved in an upcoming release of the plugin. In the meantime, please create a support ticket using the link below, so that a team member can assist in troubleshooting this individual case with you. In some cases, a workaround has been successfully applied.

https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406

Thank you.

Hi @embercide,

Thank you very much for your considered feedback.

Very happy to address each of the notes raised in the feedback above, starting with the comment about response time.

Each Afterpay Merchant is provided with a series of support channels for working through any technical challenges or concerns that may arise after completing an integration. Zendesk is our primary support channel, with response times typically within 1 business day. To date, the WordPress Support Forum has been used as a source of feature requests and enhancements for future builds – the team will continue to check the forum for feedback and commentary.

Regarding the high frequency cron task, this was explained in a separate thread. For further detail please utilise the Zendesk channel via the link below.

Very interested to learn more about the IPN challenge mentioned above. More than happy to assist in any way possible. Again, please use the link below, and be sure to include any details that may add value to the investigation.

Please raise each matter separately to the support team so that a dedicated investigation can be carried out for each case. The following form is the recommended channel for requesting technical support:
https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406
A team member will respond to each item – typically within 1 business day – providing any further details or technical support as required.

Thank you.