CryptoWoo

There was no reply so I have marked this topic resolved now. Let us know if you have any further questions.

Hi there.

When an order is created, an address is retrieved from the address list and linked to this order. You can only add addresses to the list that are unused, meaning they are not used for any orders yet and you have not received any transactions to this address on the blockchain.

To put it simply, the benefits of using one address per order (either via address list or HD Wallet)

• Ensures that payments are linked to the correct order.
• Underpayments can be detected automatically.
• Overpayments can be detected automatically.
• Great for privacy.

You should put many addresses in your address list so that you can take many orders, and as soon as you run out of addresses you must add more. If you expect many orders and/or want full automation, our HD Wallet Add-on lets you add a single master public key from your wallet an an unlimited number of addresses are generated automatically. You can get it at https://www.cryptowoo.com/shop/cryptowoo-hd-wallet-addon/

Did that answer your question?

All our premium add-ons have now also got support for HPOS.

Version 1.5.0 has been released, adding compatibility for HPOS.

We are also working on updating our premium add-ons to support HPOS and the updates will be released soon.

We were already working on adding HPOS support and the update may be released today or tomorrow.

Hi there,

We’ve triple-checked our support desk and we don’t see any tickets that we have not responded to. Could you direct us to a ticket ID so we can follow up, please?

Hi there.

We just tested MultivendorX and it is compatible. We created a vendor account, then created a product, and as a guest customer we checked out using Bitcoin with CryptoWoo.

Note that vendor commission payout is not supported. Is this a feature that you would be interested in?

Please let us know if you find any features in MultivendorX not compatible.

These are planned changes based on community feedback and are on our roadmap currently but we have no ETA on when this will be completed.

As we have not received any service desk ticket with any additional information nor here, I am going to assume it is resolved and close this topic now.

Hi there,

This certainly seems to be a theme incompatibility. Could you open a ticket on our Zendesk with some more details along with the developer of the theme and version so we can look to resolve this?

We’ve been back and forth trying to come up with a good solution for your issue but ultimately feel it’s best to propose this to you.

This is our proposed solution
* For order underpayment when the merchant does not have quote refresh setting enabled, we set the order status to a custom status called “underpaid” treated in the same way as cancelled but will make it easy to find the underpaid orders in wp-admin manually.
* For when quote refresh is enabled in settings and if the order expires, we use the amount already paid to calculate the remaining amount of BTC according to the current exchange rate and the fiat amount of the order remaining.

We’ve responded back to you on Zendesk as well but are open to anyone else willing to provide suggestions for a solution as well.

A workaround was released in version 1.0.2 as stated in the changelog:

* Add admin notice warning about missing CryptoWoo settings and possible reduction of functionality with button to install Redux Framework Plugin and additional information of file location where the Redux Framework was embedded from.

We have received a copy of the Salient theme from the theme developer, and we will work on fixing this issue in the next update.

I am happy to hear installing the Redux plugin worked for you to resolve this issue. Thanks for responding back on the solution, it is very helpful to us.

Maybe you have an alternative free theme with the same issue that you could share with us?

Hi there. We are sorry to hear about the conflict with the Salient theme. We recently updated the Redux Framework that we use because many people had compatibility issues if they used a theme with a newer Redux version or had a newer Redux plugin installed. We will look into if it is possible to support themes that load an older version of the Redux framework in the next update or to add admin notice about a workaround for such cases. We will make sure to prevent fatal errors when activating the plugin in this case.

As a workaround, can you please try to install the latest version of the Redux plugin? The Redux plugin usually loads before the theme so we think this should work. Let me know how it goes.

We would appreciate it if you can create a support ticket from our support portal on our website attach a screenshot of the error and attach the theme files. This will help us debug and resolve this issue.