[alexg]

Hello,

I cannot think of any reason why there should be such a limit. The number 29 is not significant in any way to the plugin.

I will check and get back to you.

thanks for reporting this

[alexg]

Thank you.

Glad your problem was resolved.

I will add this to the troubleshooting instructions.

[alexg]

It is possible that this is related to this problem. Could you edit the fragments.php file and see if this is solved?

kind regards

[alexg]

Hello Klaus,

Thanks for sharing the details of your project and for your interest in the plugin.

You mentioned that users of your coin have named addresses assigned. I am not sure how this works, but it doesn’t sound like this is compatible with this plugin.

Besides using the provided cloud wallet coin adapters, Bitcoin and Altcoin Wallets works best with full nodes that are forks of Bitcoin core and that share the same JSON-RPC interface. If this is the case for your coin, you can try using the Full Node Multiadapter extension. This coin adapter calls the RPC command getnewaddress on your wallet, so unless this is available, it will not work.

You mentioned that you have some coding knowledge. You can study the Coin Adapter class and see if you can extend it to fit your coin. If so, your main concern should be to provide implementations to get_new_address, get_balance, and do_withdraw.

The get_new_address() call should be able to return a new address on every call. The plugin handles the mapping between users and addresses. If you can provide an implementation that returns the assigned address of each user then it might work.

To get a sense of what a coin adapter extension looks like, you can have a look at the deprecated Litecoin adapter. This has been superseded by the Multi Adapter, but you can use it as an example of how to package a derived subclass of Coin_Adapter into a WordPress plugin.

You also asked how you can help with translations. If you wish you can consult the accompanying PDF documentation under the section “Localization”, where there are detailed instructions. The documentation is packaged in the bundle download of the plugin.

Hope this answers your questions.

kind regards

Alex

[alexg]

Yes, a number of users noticed this. My apologies.

I will release a patch to fix this.

The error is in /wp-content/plugins/wallets/views/transactions/default/fragments.php line 308.

I must have been typing “wallets” in the wrong window 🙂

thanks for reporting

[alexg]

If you have preserved user_ids by reloading the old wp_users table, then you can export the transactions to csv and reimport them.

You bring a valid point, that exporting and re-importing should be based on emails, not user_ids. I will work on the exporter/importer function so that this is easier.

For the time being, do the following: Copy the tables wp_users, wp_wallets_txs and wp_wallets_adds from your old installation to the new one. Everything should work nicely.

[alexg]

Thank you for sharing your findings. You are welcome to ask questions, this is what this forum is for.

1. There should not be too much of an overhead coming from the faucet for sites that do not use it.

2. To be clear, was the problem resolved when you installed the cloudflare extension to w3tc? If so I can instruct others who had the same problem.

Again, thank you very much.

[alexg]

Hello San,

In the latest release 3.6.0 of the plugin I have added a “fees” column to the adapters list.

You can have a look at the relevant blog post.

kind regards

[alexg]

Hello Nick,

This is now added to the latest version of the plugin, 3.6.0. The shortcode is [wallets_total_balances].

Please see the relevant blog post and the accompanying documentation for details.

kind regards

[alexg]

Hello Mc Deimon,

Some of your suggestions were included in the latest 3.6.0 release of the plugin. The points addressed were:

1. It would be good if the administrator was notified with a message when he had to accept a transaction
2. It would be good to notify a user when a payment has been sent to him (move) but still needs to be confirmed by the administrator.
3. It would be nice to be able to have a transaction confirmed by the administrator automatically after a time defined by the administrator (for example 5 days)

Please see the relevant blog post and the accompanying documentation for details.

Your other suggestions might be included in a later release.

kind regards

[alexg]

Hello San,

In the latest version 3.6.0 you can now display exchange rates with the [wallets_rates] shortcode or widget.

Please see the relevant blog announcement and the “Frontend” section of the accompanying documentation.

kind regards

[alexg]

Hello,

Problem 1:

To be clear, can you please confirm this?

1. The parent plugin, Bitcoin and Altcoin Wallets, is network-activated on your multisite install?

2. You have installed and activated the Faucet extension on a single site? This should normally not be possible.

Perhaps you have also single-activated the parent plugin. You should not be able to see the Faucets menu item. Your wallets menu item should be under network settings.

Try deactivating the parent plugin from the network menu, and then see if the plugin is also activated on your single site admin screens. This is not a valid configuration.

Problem 2:

The time limits are based on WordPress transients. In some server configurations it seems like WordPress transients do not expire, and I am currently trying to determine why. This does not appear to be a problem with the plugin, but might be a misconfiguration of the server’s object cache. Unfortunately I do not currently know more about this. But your problem could also be caused by having the faucet extension activated on a single site while the parent plugin is network-active. We must first resolve problem 1 before addressing problem

In general, you can install the parent plugin network-wide and then do the same with the faucet extension. You can install the faucet extension at the network level and then only use the faucet shortcodes on the sites where you need it.

kind regards

[alexg]

In the upcoming release 3.6.0 of wallets it will be possible to see total fees paid per coin.

I do plan to provide more detailed statistics in the dashboard area in some future release.

thanks

[alexg]

The reason for the discrepancy is that when the addresses table is first created, it is created with a table-wide default encoding of latin1, since it does not need to contain any Unicode data. The dbdelta() function that WordPress provides does not handle encodings, and therefore I have some manual alter table queries in there to ensure that some columns do not generate indexes that are too large for some old versions of MySQL. The encoding for enum types is not really important, as the possible values are enumerated and therefore take up fixed space when indexed.

Bottom line is, I am currently unable to verify that changing to a different encoding would solve a reproducible issue.

But if another encoding or collation works for you, then go ahead and use it. You should not have any problems doing so.

kind regards

[alexg]

Hello,

Sounds like you are trying to configure a full node RPC adapter and are hitting a firewall.

Firewalls usually cause timeouts and slow down your site.

See the paragraph “When I activate the plugin, my WordPress becomes extremely slow and is unusable.” in the troubleshooting section of the documentation for a short discussion on this.

Generally this is a networking issue. Once you make sure that RPC connections are possible the error should go away.

kind regards

[Author]

Posts