[alexg]

This is now implemented in 3.0.2

All the coin UIs and the custom menu item now display coin icons.

[alexg]

Hello,

I do plan to add this in the near future.

Almost all the work is in the plugin, but the knockout templates are not bound to the image.

In the meantime, if you are interested to get the image url of the currently selected coin, it is returned with this javascript:

wp.wallets.viewModels.wallets.coins()[wp.wallets.viewModels.wallets.selectedCoin()].icon_url

I will try to add image display into the UI templates soon.

thanks

regards

[alexg]

Hello,

Thanks for your feedback. For most coin adapters, you can already set move and withdraw fees.

For the CoinPayments adapter you cannot, however the withdrawal fee is set by the platform to some sane defaults.

A minimum amount for withdrawals is already implied, because whenever you set a withdrawal amount, the withdrawal fees are subtracted from it. If a user is willing to pay the fees, no matter how small their withdrawal is, there will be no cost to your site.

Note that the proportional withdrawal fee that you set in your CoinPayments “Fees” tab is paid *in addition* to the withdrawal fees set by the CoinPayments platform.

kind regards

[alexg]

What you describe could be done, however it is a different plugin altogether.

I am writing down your suggestion and hopefully I can visit it at some point.

Thank you

[alexg]

Hello,

Unfortunately the fact that you found a 2FA plugin is not helpful to me. To implement a 2FA solution, the hard part is actually integrating it to the plugin, not finding a plugin that already uses such a solution. Thanks for the suggestion, I might implement it later if I find some time, however for the time being I would recommend that you work on your email issues. There is no reason why sending email should not be reliable. As you said, using an SMTP plugin might be a good idea, if the default mail capabilities on your server are not correctly setup. The one I’m using is https://wordpress.org/plugins/wp-mail-smtp/

thanks

[alexg]

Thanks for reporting this.

Did you try to disable the exchange rates in Wallets -> Rates? Does the problem occur then?

Pulling exchange rates is something that takes a long time but it is done on the WordPress shutdown action, and therefore should not slow down the request. However it might be related.

[alexg]

Thank you for testing, I am glad it worked. A lot of work has gone into performance improvements.

kind regards

[alexg]

Hello,

I would not recommend that you delete the transactions table because this will delete the user transactions. The transactions might be picked up again or they may not, depending on how many there are. Instead I would recommend that you do the following:

1. Keep a backup of your live database. You can use mysqldump of phpmyadmin to do this, or any other method that you are familiar with as long as you are certain that you can restore the backup in case something goes wrong.

2. Deactivate the wallets plugin to make sure that people are not using it.

3. Make sure that your coin adapter has “CLAM” everywhere where it’s needed instead of “CLAMS”. Install the new adapter.

4. Assuming the DB table prefix is wp_ do the following in your SQL console:

UPDATE wp_wallets_txs SET symbol=’CLAM’ WHERE symbol=’CLAMS’;
UPDATE wp_wallets_adds SET symbol=’CLAM’ WHERE symbol=’CLAMS’;

5. Enable the wallets plugin again.

I cannot think of any reason why this should not work. But still keep a backup of your live database before you do this.

let me know how it goes

kind regards

[alexg]

Update: Can you please check to see if the problem is resolved in version 3.0.1? Thank you.

[alexg]

Another thought, in addition to the ones above:

Can you please try again with Wordfence disabled? It could be that the plugin’s rules are blocking the new JSON API.

[alexg]

Note: Others have reported this same issue at https://wordpress.org/support/topic/could-not-contact-server/

[alexg]

Thanks for reporting.

This looks like a misconfiguration on your Apache server’s htaccess. I believe it is a different issue than the original one where you reported problems with the CoinPayments platform. Something is triggering a loop of redirects.

Did you change something in your .htaccess?

When does the error message appear in your logs? Does it occur on all page accesses?

[alexg]

Hello,

Thanks for reporting. Could it be that you have not refreshed your page? Version 2 of the JSON API requires the new JavaScript.

Also, as a test, does the problem persist when you enable “legacy APIs” in your frontend settings?

let me know please

Thanks.

[alexg]

Thank you for reporting.

This is usually an issue with one or more wallets on CoinPayments being temporarily down for maintenance.

When you first reported an issue with Bytecoin I remember distinctly that the wallet was down for maintenance. Probably your transaction went through now that the wallet is back online.

This is an unavoidable drawback of relying on a third-party service.

kind regards

[alexg]

Yes can you please tell me which of the two available CAPTCHA types does not work? reCAPTCHA or SolveMedia?

Are you logged in? Do you see any error message either in the page or at your JavaScript console (F12)?

Thank you

[Author]

Posts