Afterpay
Forum Replies Created
-
Forum: Reviews
In reply to: [Afterpay Gateway for WooCommerce] Excellent Support Via The Support ForumHi Gary,
You are correct, there is a syntax error in the code provided above. The line before the line with
$bool_result=false;is missing a closing parenthesis. It should read as follows:if (array_intersect( $product->get_category_ids(), array(1, 3) )) {Please excuse the mistake. Let us know how you go with the amendment above.
Thank you.
Forum: Reviews
In reply to: [Afterpay Gateway for WooCommerce] Excellent Support Via The Support ForumHi @zulu11,
Thank you for your honest review of the plugin. The engineering team here on WordPress.org (the authors of the plugin) are more than happy to assist with this challenge.
The
afterpay_is_product_supportedhook (documented here) can be leveraged to achieve the outcome described above. If a callback function is attached to this Filter with two arguments, the second will be populated with a WC_Product object. This object exposes a method called get_category_ids, which can be used to exclude Afterpay from a given list of Product Categories.For example:
/** * @param bool $bool_result * @param WC_Product $product */ function afterpay_ips_callback( $bool_result, $product ) { # Categories #1 and #3 don't support Afterpay. if (array_intersect( $product->get_category_ids(), array(1, 3) ) { $bool_result = false; } return $bool_result; } add_filter( 'afterpay_is_product_supported', 'afterpay_ips_callback', 10, 2 );Please try to implement something similar to the above inside the active theme’s
functions.phpfile, replacing the category IDs as needed. Don’t hesitate to reply back to this thread if further support is needed.Thank you.
Hi @sudobash,
Thank you for your message.
Seems like this online store is running an outdated version of the Afterpay plugin. Please see details in https://wordpress.org/support/topic/re-woocommerce-afterpay-gateway-v1-3-1/
Upgrading to the latest version of the plugin should be able to address the challenge.
Thank you.
- This reply was modified 5 years, 9 months ago by Afterpay.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Shortcode For Divi Builder Not WorkingHi @thunk303,
Thank you for your message.
We are glad that the issue has been resolved.
Regarding the plugin versions:
- Version 1.3.1 was the latest version of the WooCommerce Afterpay Gateway plugin. This iteration of the plugin was never published on the WordPress SVN.
- For the purposes of following naming conventions for all WordPress plugins, the Afterpay plugin was renamed to Afterpay Gateway for WooCommerce, and version 2.0.0 was published via the SVN on Friday, 13 July 2018.
- Due to the different name, there is no prompt to upgrade for versions prior to 2.0.0. The recommended practice is therefore to deactivate and remove the old plugin, then install and activate the new plugin by following the steps documented here: https://developers.afterpay.com/afterpay-online/docs/woocommerce-install-plugin
- Plugin configuration settings will not be removed when the plugin is uninstalled. It is considered best practice to complete these steps in a staging environment prior to making any changes in the production environment.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] AfterPay Appearing above page contentHi @thunk303,
Thank you for your message.
Could you try using the shortcode workaround as discussed in the other post https://wordpress.org/support/topic/shortcode-for-divi-builder-not-working?
If that still does not resolve the issue, the team would be happy to assist with an investigation. Please submit a dedicated support request from the Afterpay Help Centre here:
A team member will then reach out to you within 1 business day.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Shortcode For Divi Builder Not WorkingHi @acephalia,
Thank you for your question.
The Payment Info on Individual Product Pages is by default located under the price, because that appears to be the most suitable place for that message.
However, there is a temporary workaround for this particular use case. The hook name can be set to a non-existent hook, while leaving the ‘Enable’ on and not deleting the paragraph text. For example, change the hook name from ‘woocommerce_single_product_summary’ to ‘afterpay_removed’. That way, it would ignore the default location and show up only where the shortcode is inserted.
The engineering team is currently investigating this challenge further, and plans to improve this shortcode feature in the next release of the plugin.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Plugin not workingHi @ajaysing,
Thank you for your message.
The team would be happy to assist with an investigation. Please submit a dedicated support request from the Afterpay Help Centre here:
A team member will then reach out to you within 1 business day.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] unsupported_currency errorHi @samp1411,
Glad to hear the challenge has been resolved. Thank you for following up.
The Sandbox environment does not send SMS messages. When prompted for an SMS verification code, please enter 111111.
For further guidance testing in Sandbox, please see the following resource:
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Add Woocommerce Block SupportHi @webkix,
Thank you for submitting this feature request.
A corresponding internal ticket has been raised with the engineering team for investigation and potential for inclusion in future roadmap discussions.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] unsupported_currency errorHi @samp1411,
Thank you for your message.
The Sandbox merchant account in use here is registered for trading in Canada, so it can only process transactions in Canadian Dollars (CAD). If a US merchant account is required for Sandbox testing, please reach out to the person who provided you with the CA merchant account.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Undefined variable on line 846Hi @kyle-tully,
Version 1.3.1 was the latest version of the “WooCommerce Afterpay Gateway” plugin. This iteration of the plugin was never published on the WordPress SVN. For the purposes of following naming conventions for all WordPress plugins, the Afterpay plugin was renamed to “Afterpay Gateway for WooCommerce”, and version 2.0.0 was published via the SVN on Friday, 13 July 2018.
Due to the different name, there is no prompt to upgrade for versions prior to 2.0.0. The recommended practice is therefore to deactivate and remove the old plugin, then install and activate the new plugin by following the steps documented here: https://developers.afterpay.com/afterpay-online/docs/woocommerce-install-plugin
Plugin configuration settings will not be removed when the plugin is uninstalled. It is considered best practice to complete these steps in a staging environment prior to making any changes in the production environment.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Undefined variable on line 846Hi @kyle-tully,
Thank you for your message and for providing detailed information.
The files referenced in these PHP notices do not match any files in the current version of the Afterpay Gateway for WooCommerce plugin. It’s possible that an outdated or unofficial copy of the plugin is being used. Further information may be required to confirm this preliminary conclusion.
The team would be happy to assist with further investigation, and assistance with updating or reinstalling the plugin if required. Please submit a dedicated support request from the Afterpay Help Centre here:
A team member will then reach out to you within 1 business day.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Afterpay Hook PriorityHi @drewblu,
Thank you for your message.
Changing the priority can be helpful when multiple functions are attached to the same hook. In this scenario, the priority determines the order in which the attached functions are executed. If there is only one function attached to the hook, the priority value has no effect.
Some suggestions may include identifying a different, more appropriate action hook (or creating your own), then configuring the Afterpay plugin to use it.
The team would be happy to assist with an investigation. Please submit a dedicated support request from the Afterpay Help Centre here:
A team member will then reach out to you within 1 business day.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] Compatibility issues causing a mess.Hi @mvincik,
Thank you for your message.
The team would be happy to assist with an investigation. Please submit a dedicated support request from the Afterpay Help Centre here:
A team member will then reach out to you within 1 business day.
Thank you.
Forum: Plugins
In reply to: [Afterpay Gateway for WooCommerce] CompatabilityHi Colin / @tbjv,
Thank you for your interest in Afterpay. There are no known compatibility challenges between the “Afterpay Gateway for WooCommerce” and “WooCommerce PDF Product Vouchers” plugins.
Merchants are encouraged to test their unique combination of plugins and configurations in a staging environment to verify compatibility prior to installing in production.
Thank you.