dashed-slug.net

OK. Thank you for the additional info.

What happens if you:

1. Deactivate all plugins (do not uninstall)
2. First install and activate Bitcoin and Altcoin Wallets
3. (assuming your site is still up) disable the built in coin adapter.
4. Then, finally install/activate the CoinPayments adapter.

Also, you mentioned there are no firewalls at the level of the host. Could there be a firewall around your host’s network?

Thank you for this amazing review!

I’m very glad that you found the plugin useful.

Alex

If you uncheck fixer from the list of exchange rates providers, the plugin will not use the remote API. Also, if you do not provide an API key, the plugin will not use the remote API.

The last exchange rates that were loaded will be used. If you wish to delete these, you can delete the option wallets_rates. If you are using wp-cli you would do wp option delete wallets_rates.

If the WooCommerce default currency is the same as the one that the user is attempting to pay with, then you do not need any exchange rates providers for the payment gateway extension to work.

Hope this helps. Let me know if you face more problems with this.

• This reply was modified 7 years, 8 months ago by dashed-slug.net. Reason: added paragraph about plugin always using last rates retrieved

Hello,

Are you trying to connect to a full node wallet or to a web wallet?

If the latter, there is no need to disable anything. Simply disable the build in full node wallet, as detailed in the installation instructions.

If indeed you are attempting to connect to a Bitcoin core wallet, then timeouts are always caused by some type of firewall, either at the WordPress machine or the wallet machine, or anywhere in between.

Please let me know which type of coin adapter you decided to use.

Thanks

If your site does not work anymore, simply delete the plugin from your plugins directory using SFTP, then read the Troubleshooting section in the manual, under “When I activate the plugin, my WordPress becomes extremely slow and is unusable.”

Most likely you have not disabled the built-in Bitcoin full node adapter while some firewall is in effect and is blocking RPC connections.

kind regards

Hello Felty,

I also get this question a lot, in fact I should add it to the FAQ.

I do not recommend that people use WooCommerce and the WooCommerce payment gateway extension to sell tokens or other coins.

Instead I point people to my other extension, the Exchange extension. It is still in late beta, but it allows admins to set up markets using currency pairs. Users can therefore log on, send a cryptocurrency to their account, trade it for some other cryptocurrency, and withdraw it. This requires that there is a coin adapter that supports the coin/token being sold.

Additionally, I will soon™ release a fiat coin adapter. This will let admins do fiat deposits from bank transfers. This is the other thing that people often request along with selling tokens. This will be announced on the blog when available.

Hope this answers your questions. Please let me know if you have any further questions about this.

with regards,
Alex

Thank you to all who reported this problem.

The issue is fixed in version 3.6.6.

TL;DR explanation:

All of you are using very ancient versions of MySQL; your hosts should be ashamed! This is not a problem on its own, but since the default charset is set to utf8mb4 to accommodate the full Unicode set, some indexes on large columns go over the limit of 1000 bytes that these old databases had. Previously I had set those columns to the latin1 character set to avoid this problem. But this had caused problems for other people. In any case, the columns are such now that even if these two conditions exist (old database + utf8mb4), the total index length does not exceed 1000 bytes. Transaction IDs now can go up to 120 characters, while Monero addresses do not exceed 106 characters, so this is enough for all coins. I was able to verify with MySQL 5.5 via Docker that the new schema no longer causes error 1071.