[alexg]

That link is the CoinPayments adapter page. There are no PDF documents there. The manual is found the bundle download of the plugin, available at the downloads section: https://www.dashed-slug.net/downloads/

You did not mention if you checked your capabilities. Most probably you have not assigned has_wallets to the subscriber role.

Do download the documentation. It will save you time.

[alexg]

This is a very common issue people have when they first use the plugin.

Please check the PDF documentation under the heading “I do not see the UI elements in the frontend.”

There are a number of reasons why this is so. Check and let me know.

regards

[alexg]

You’re welcome.

[alexg]

You would get this error if one of the codes you entered was not exactly correct.

Enter the codes again and make sure that you do not add any spaces next to the codes.

After entering the codes again, save changes and wait for two minutes before refreshing your page again.

[alexg]

No, you will need to disable it if you want to use Bitcoin with CoinPayments.

The plugin should be warning you about this.

[alexg]

Hi,

Why did you enable Tor? Are you setting up your website as a hidden service?

If not, disable tor and check your adapter status in the “Adapter” screen. If successful, the adapter status should read “Responding”.

You will also need to setup the IPN secret as detailed in step 8 of the installation instructions.

[alexg]

Hello,

The CoinPayments adapter extension is available on this site at https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/coinpayments-adapter-extension/

There are instructions and a troubleshooting section on that same page. The main plugin also has an accompanying PDF document which you might like to have a look at.

The error you get is because you have not connected the built-in Bitcoin core adapter to a running wallet. Simply disable the bitcoin core adapter. The plugin will instruct you about this.

regards

[alexg]

Thanks for reporting this Jack and apologies for the late reply. I will look at this as soon as possible.

regards
Alex

[alexg]

Hello Ed,

Users can have a wallet when they have the has_wallets capability. By default, users have the “Subscriber” role which does not have that capability by default. Please see Wallets -> Capabilities to see which capabilities you may need.

Normally this Capabilities UI should be all you need, but in multisite setups it won’t help you because the wallets menu is available at the network level, not at any individual site.

I will try to address this in a future release, but in the meantime you can use any plugin for managing capabilities to assign has_wallets to “subscribers” on each blog where you need it.

This plugin is quite good: https://wordpress.org/plugins/user-roles-and-capabilities/

hope this helps

kind regards,
Alex

[alexg]

The missing tables issue is now slved in 2.10.0

[alexg]

Hello,

Thanks for being so patient. Turns out the last couple of versions had an SQL bug. I am preparing a release that will fix this SQL bug among some other things. It makes more sense to try to diagnose your issue with this latest version, because it might be related. I hope to get the fix out today. I will make a note to contact you after that. Don’t worry about documentation that’s not a problem but thanks for offering to help.

regards
Alex

[alexg]

Following up from my previous post, I believe I have isolated the issue:

Due to an error on my part, if the tables do not exist the plugin does not create them immediately on activation, but after the first run/request. I will fix this.

If you only saw the error once and no more then that means that the tables are created now and you can proceed.

If the error persists, deleting the wallets_db_revision option will do the trick.
With SQL: DELETE FROM wp_options where option_name = 'wallets_db_revision';
Or with cp-cli: wp option delete wallets_db_revision.

Refresh your WordPress and your tables should be created.

Or simply wait until the next patch.

Apologies for the confusion.

regards

[alexg]

Hello,

If the table is not created correctly you will definitely not be able to perform transactions. This is why the plugin is warning you.

This is an issue that was fixed in a past release. I assume you have already checked that you are installing the latest version.

If that’s the case, I recommend that you drop the two tables and reinstall, this time taking note of any errors in the logs. That’s the only way to know what went wrong. The plugin has been tested with PHP 5.6 and it should work.

Do let me know what you find.

regards

[alexg]

OK, there was no chance for what you did to work. Private addresses do not offer a way for the plugin to be notified. That’s why callback addresses (commercial) are used instead. The plugin needs to generate these addresses as needed.

So we will first need to find out why addresses are not being generated (or not stored to the database). You are quite right, it is indeed a very strange situation. But this is the root cause of your issues.

Two things that come to mind:

1. I am not convinced that there are no errors in your logs. There should be at least some warnings, even if everything works as expected. More likely, there should be some error indicating either that the plugin could not contact the platform or that it cannot insert a new address to the database.

2. After clearing the tables, did you first visit the page with your [wallets_deposit] UI? This is what triggers a new address to be generated, when a deposit address does not exist.

Other than that, I cannot think of anything else right now. Once I think of something I will get back to you.

[alexg]

Can you please explain what you mean by “I made a new one”?. The litecoin testnet page has its own address (see the “wallet address” field). You can test withdrawing to that address. Or, if you have created a new address in some other litecoin testnet wallet that will work too. You cannot withdraw to another address generated by the same plugin. If you do, then your withdrawal will be automatically changed to an internal transfer.

Did you check the things I asked you in the previous post? What did you find?

[Author]

Posts