[alexg]

Hello,

If you want to provide a CLAM adapter, you might find it easier to do this using the new multi-adapter, which works for many coins:

Full Node Multi Coin Adapter extension

You should then have no problem implementing a CLAM faucet.

It is possible that PayPal does not accept your bank or credit card.

You are welcome to pay for membership via cryptocurrencies if you wish.

Please send the equivalent of $9.95 at one of the following addresses and I will activate your three month membership manually.

Bitcoin Address: 1DaShEDyeAwEc4snWq14hz5EBQXeHrVBxy
DOGE Address: DASHEDj9RrTzQoJvP3WC48cFzUerKcYxHc
LTC Address: LdaShEdER2UuhMPvv33ttDPu89mVgu4Arf

kind regards

[alexg]

Hello,

Yes this is expected behavior. The plugin’s job is not to enforce any SSL policy on your website – it simply warns you if you are not using SSL. The correct place to enforce such a policy is at your web server’s configuration (Apache or Nginx, usually).

kind regards

[alexg]

Thank you I am investigating this.

[alexg]

In that case, is it possible for you to check again after disabling your other plugins? The problem should not be caused when the other plugins are disabled. Then re-enable them one by one to find out which one causes the problem. Once you do, let me know and I will test with that plugin on my end and fix any problem.

Additionally, can you check your .htaccess file, if you are using the apache server? The recommended settings are here: https://codex.wordpress.org/htaccess If your .htaccess file differs from the one recommended, can you send it to me?

please let me know what you find

thank you

[alexg]

Unfortunately this is not how it works. A get parameter does not take you anywhere on its own.

The WordPress system, and occasionally, some themes or plugins interpret your get parameters and can do anything they want with them, including redirect you. This is why I have prefixed the parameter with the plugin slug as is best practice (__wallets_faucet_ref). This ensures that the parameters in the faucet plugin is not used by other plugins.

Have you established that this is caused when that particular theme is activated? What happens if you switch to another theme?

[alexg]

Hello irbexchanger,

The error you mentioned indicates that the DNS name coinpayments.net was not resolved by your server, possibly due to bad internet connectivity. I assume that the error should have resolved by now. If not, it would indicate misconfiguration of your DNS system, and this should be addressed by your server host.

I have moved your post to a new thread. In the future could you please open a new thread whenever you experience a new issue? The thread you posted on was opened for something completely different.

Thank you

kind regards

[alexg]

Hello,

Thank you for the two improvements that you suggested. Unfortunately, the plugin cannot currently do these things.

For displaying the [wallets_balance] shortcode in an alternate fashion, what is required is a different knockout template. There are instructions in the manual on how you can provide a different directory with knockout templates. I would imagine that it will involve the foreach binding, to iterate over the coins() observable.

For your second suggestion, this is not possible at the moment. At some point in the future, I will allow shortcodes to take optional arguments, and then you will be able to specify a coin or other constraints on what is displayed. This is a big task and I cannot do it at this time.

kind regards

[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

[Author]

Posts