mohsinoffline

Hi Stan,

Thanks for using our plugin. I think you answered your own question there. Ideally, no plugin or theme should add jQuery from anywhere except enqueuing the default from WordPress. The checkout page markup containing multiple instances of <script> tags embedding the jQuery library, will create a conflict that will most likely have a knock on effect on any function that relies on jQuery. Does the theme not allow you to disable the additional instance of it?

@all

At the moment, it seems the issue is between NMI’s Collect.js library and the DuckDuckGo browser. Also DuckDuckGo spoofs as a different browser, so there is no reliable way to detect it and turn off tokenization just for the customers using that browser.

Here is the reply I received from NMI when I reached out to them:
https://tinyurl.com/2acfmr7f

If you need to turn off Collect.js, you can remove the public tokenization key from the settings. However, this should only be treated as an interim measure and when Collect.js is compatible with DuckDuckGo, it is best to enable it again.

Closing due to no further follow up.

Closing due to no further follow up.

Closing due to no further follow up.

Hi there,

So you have a URL to check?

Hi Karim,

No, for the plugin to work (free version hosted on www.remarpro.com), CIM is not required to be active.

Hi there, can you please post the URL of your site to check?

Closing this. It seems the SSL updates went through without creating any issues.

Hi there,

The plugin as supported HPOS from the moment it became a thing. Please let me know if you face any issues after switching to HPOS in a staging environment.

If you update to the latest version 6.1.11 and if you prefer to manually approve transactions, you should be able to turn off auto-capturing on status change by unchecking the “Capture authorized transaction on status change” option.

@jkohlbach I noticed the same issue on a customer site. It happens when the cart amount is 0, seems like the IGFW_Order_CPT::show_invoice_payment_gateway_on_free_orders() method empties the list of available methods using the following line:

WC()->payment_gateways->payment_gateways = array();

Please let me know if you need help recreating the issue.

• This reply was modified 4 months, 3 weeks ago by mohsinoffline.

Hi there,

This could happen if you are already approving the transactions in Authorize.Net and then changing the order status in WooCommerce, but please let me know if that is not the case with you.

If you change the status of the order to “Processing” without approving it in Authorize.Net, the plugin will do it for you automatically. When you have approved it prior to the change of status, the plugin puts sets the status to Failed once because it is trying to capture the funds, but cannot, since you already captured them in Authorize.Net.

Basically the plugin itself uses WP’s built in wp_remote_post() function to send the API requests and does not specify a certificate to be used. This, to my knowledge would use the root certificates installed on your server. It is best to check with your hosting if the change of SSL/TLS certificates on Authorize.Net’s side would affect the site’s communication with the API endpoints listed below:

Sandbox: apitest.authorize.net
Production: api.authorize.net

@all

This should not impact the plugin. However, we will still follow the developments and will make any necessary changes to the plugin in advance in case there is a need.