[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?

[alexg]

OK you have a somewhat strange problem indeed! Never come accross this one.

I find it very curious that your IPN history is empty. I assume that by “removed all data” you mean that you also emptied the wp_wallets_adds table. As I mentioned before, this data is not deleted when you uninstall the plugin.

Here’s what you can check:

Every time the plugin requests a new deposit address, a “callback address” is generated on the CoinPayments platform. You can then view these callback addresses via the dashboard. For Litecoin testnet, navigate to https://www.coinpayments.net/index.php?cmd=acct_balances&action=deposit&coin=LTCT

You should see your deposit address listed there. It’s type should be “commercial”. If that’s the case, then when you send funds to that address the platform should attempt an IPN to your site, regardless of what the plugin, or anything on your server, does.

[alexg]

Hello,

First of all yes, this is the right place to post issues with the plugin. For issues that are about the main plugin you may also post at the wordpress.org forums, but here is fine too.

As for your particular issue, the UIs will only show when there is at least one adapter that is in “responding” status. So this is expected behavior.

You may also refer to the “troubleshooting” section in the PDF documentation, under “I do not see the UI elements in the frontend.” I try to keep a record of the most common issues people face.

regards
Alex

[alexg]

Hello,

I believe what is happening is this: You generated a deposit address while you had entered an IPN URL. This didn’t work because the IPN URL, if present, should end with ?wallets-cp-ipn=1 . Then I told you to remove the IPN URL but the deposit address you had generated still had a faulty IPN. When you uninstall the plugin, the tables are not being deleted. This is done for safety. So the old deposit address remains. You could try to empty the addresses table. This will force the plugin to regenerate new deposit addresses. You can do this with the following SQL query:

TRUNCATE wp_wallets_adds;

making sure to replace wp_ with whatever your table prefix is. Then, try a new deposit to that address. If you want to test with LTCT, you can use this faucet to send testnet Litecoins: http://testnet.litecointools.com/

Try this and wait a few minutes. The deposit should work.

If not, we will need to look at the following:

1. Does the [wallets_deposit] shortcode show you deposit addresses?

2. Are there IPN attempts in your IPN history?

3. If there are IPNs what is their status? The CoinPayments platform lets you view whether an IPN message was received or not.

4. Are there any errors in your logs? Instructions for enabling the logs are here: https://codex.wordpress.org/Debugging_in_WordPress

Apologies, but I only offer support over email and the forums. This is also mentioned in the terms of service. There are good reasons for this. I do try to reply as quickly as possible whenever I am not sleeping or away from work.

Give this a try and let me know. Hopefully it will work now, but if not, please answer the above questions so we can find out what’s wrong.

kind regards

[alexg]

I have not yet found the reason why the plugin did not work to begin with.

The SQL I sent you was exported from my machine. Most of the collation and charset directives are not needed. Only the ones that refer to the latin1 charset. You should be OK with MySQL 5.5. I have edited the SQL code and removed any unnecessary charsets. Your system should now use whatever is default for the columns where it doesn’t matter.

So please do another attempt. Use the same pastebin link. I have edited it.

[alexg]

Additionally, try leaving empty the IPN URL altogether. There is no need to specify this as it is being set by the plugin on each callback address. The full IPN URL constructed by the plugin is something like http://example.com/?wallets-cp-ipn=1 but you do not need to worry about this.

[alexg]

Thanks, I didn’t know about this. I had never tried IPN with IP addresses instead of domain names.

To clear up any confusion:

Every time you send cryptocurrencies to a deposit address, CoinPayments will do an HTTP request to your site. We need to know 1) if it is being sent and 2) if it is being received. The “IPN history” page allows you to see both of these things. The screenshots you sent earlier indicated that no messages were being attempted. Probably due to the missing trailing slash.

At the very least you should now be seeing IPN attempts on CoinPayments, even if the messages do not arrive at your site.

Let me know how it goes.

regards
Alex

[alexg]

Hello,

A few people have reported this issue in the last couple of days but I was unable to reproduce the problem in a number of setups.

Is it possible for you to enable logs and send me whatever gets written out while you activate the plugin? Instructions for enabling logs are here: https://codex.wordpress.org/Debugging_in_WordPress This will help me know what’s wrong and what to fix.

Alternatively you can use the following SQL code in your console, to create the tables manually.

https://pastebin.com/huhbVPDT

The above code assumes that your DB prefix is wp_. If it is something else, you will need to replace the table names.

[alexg]

OK, first things first.

I only mentioned the csv export because I thought you wanted to migrate an existing transaction from one machine to another. If you have not performed any successful transaction yet, just ignore the export/import thing.

Also, if your IPN history is empty, that means that the CoinPayments platform never attempted to notify the plugin of any deposits. Could it be that you have not setup IPN correctly? Please confirm that you have followed the installation instructions on https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/coinpayments-adapter-extension/ and in particular the part where you create an IPN secret and set in the coin adapter settings.

[Author]

Posts