[alexg]

Hello,

Thank you for reporting this and for providing the screenshots.

Obviously something is going on here since you are the second person reporting this problem.

However I have not yet been able to reproduce the problem.

I will continue looking into this and will report back here. There’s a few more things I need to try.

kind regards

[alexg]

Thank you for your very kind words!

It is true that the first four of these ideas are already tickets in my backlog.

I will add the fifth too.

At the moment I have concentrated all my efforts into finalizing the exchange extension and preparing the release. There’s also some improvements that need to be done to the dashed-slug website and I plan to prepare a large amount of instructional videos about the plugins right after that.

I will continue to improve the main plugin shortly after releasing the exchange.

Thank you for your feedback, it is very valuable to me.

kind regards

[alexg]

Yes, thank you for the clarification. I believe I understood you correctly.

If you want to delete transactions altogether and not leave any trace, you would have to delete it from the database, such as using the MySQL CLI or a phpmyadmin interface.

For example to delete all the transactions from the faucet:

DELETE FROM wp_wallets_txs WHERE tags LIKE '%faucet%' AND category='move';

Additionally: In light of the recent changes to privacy regulation, due to GDPR, there is also a feature that lets you delete all the transactions of a user. If a user requests their personal data to be deleted, in WordPress 4.9.6 and later you will be able to completely wipe a user’s personal data. The plugin is already built to support these upcoming changes and will delete all the transactions that belong to a user when an admin deletes that user. The admin simply has to click on Tools and then Erase Personal Data to initiate the erasure process for a user. The user will have to provide consent over email.

kind regards

[alexg]

Hello,

It looks like you are 90% there.

I believe the problem is that you are first trying to bind the function and then you define that function. Also, you don’t need str_replace. Try something like:

function change_text($comment) {
  $comment = "leave a message";
  return $comment;
}

add_filter( 'wallets_ui_text_comment' , 'change_text');

The reason you just get a blank page and not an error message is that you have not enabled errors. If you try the above and it still does not work, follow the instructions here: https://codex.wordpress.org/Debugging_in_WordPress to enable logging.

Let me know if you still have problems with this.

kind regards

[alexg]

Internal transactions (i.e. those that are not deposits or withdrawals) can be cancelled by an admin. Cancelling a transaction makes it no longer affect user balances, but the details of the transaction remain. If you wish to delete a transaction altogether, you can delete it from the database.

Hope this answers your question.

kind regards

[alexg]

If you have the latest version (1.3.4) of the faucet extension then there is no reason why the countdown would not show.

If the captcha is displayed, and if there are no JavaScript errors in your console, then the timer should be displayed. You can disabling the other plugins just to test if there is any incompatibility with another plugin that you use.

Additionally, you can email me some credentials to login and have a look at your DOM.

I will be able to determine if the countdown markup is rendered in your HTML and if it is hidden by some CSS or some other means.

kind regards

[alexg]

Hello,

The path is normally not needed. It would only be relevant in very special circumstances if the API has been mapped to a URL path. You should leave it empty.

The wallet passphrase should match whatever you have set as your walletpassphrase when you encrypted your wallet. You only need to set this if you want to enable withdrawals, and only if you have encrypted your wallet (you should).

To connect to a remote wallet, you first need to make sure that your firewalls are configured correctly on both ends. If they are not, you will get connection timeouts which will slow down your site.

You must also do ssh tunneling (see https://en.bitcoin.it/wiki/Enabling_SSL_on_original_client_daemon) to make sure that communication is secured. It has been requested of me to add instruction on how to do this but I have not had the time to attempt it myself. So I cannot provide instructions. This is a question better suited to the Bitcoin core wallet developers.

You might also want to look at ways to maintain an SSL tunnel open. This is more of a sysadmin question, so have a look here: https://superuser.com/questions/37738/how-to-reliably-keep-an-ssh-tunnel-open

Eventually I do hope to be able to provide more assistance on this. I will provide some instructions in the manual when time permits.

I do hope that I have at least pointed you in the right direction. Do let me know if you have more questions.

kind regards

[alexg]

Hello again,

You can now set the originator address and name more easily in the admin section, in version 3.3.1 of the plugin.

You can find the option in Admin → Wallets → Notifications → Notification settings for ALL events. This also affects e-mail confirmations.

regards

[alexg]

Hello,

This is now addressed in 3.3.1. In your email templates you can now use the value ###CREATED_TIME_LOCAL### instead of ###CREATED_TIME###.

regards

[alexg]

Hello,

You can use USDT in version 1.0.3 of the CoinPayments adapter.

regards!

[alexg]

Hello,

Thanks for providing a detailed description of the issue. Your funds are safe in your wallet, it’s just that they were not credited to that WordPress user in the DB.

1. You have verified that the IPN endpoint is accessible from your browser, but it also has to be accessible from CoinPayments. If you are filtering IPs by geolocation on your site then that could be one problem.

2. A security plugin could be blocking the IPN message. If this is a test site, you could try to disable your security plugins and try again. If the message works this time, this means that your security plugins need configuring.

3. You say that the IPN message was not sent. If you open up the details of the message in your CoinPayments account there might be more information there. Go again to the IPN history, find the message with status = 100 and click on the date/time on the left hand side. This will open the details of that message and there might be an error message there. If there is, please share it with me so we can figure out what happened.

You do not need to test with real crypto, you can test the mechanism with LTCT to make sure that everything works as expected. You can initiate Litecoin testnet deposits from here: http://testnet.litecointools.com/ The IPN mechanism is exactly the same for all coins.

Please keep me updated.

kind regards
Alex

[alexg]

Hello,

This is intentional.

I am not sure the plugin would work with some wallets offered by CoinPayments so I’ve left them out.

I will have to review whether USDT could work and maybe re-enable it if it does.

regards

[alexg]

Hi, the plugin sends emails with the wp_mail() function. So you could to follow the instructions given here:

wp_mail()

You could hook into the filters wp_mail_from and wp_mail_from_name somewhere in your functions.php. Here’s how to do this:

https://codex.wordpress.org/Plugin_API/Filter_Reference/wp_mail_from

The above will affect all email sent with wp_mail() from your site.

I will make a note to make it easier to set an originator for the plugin via an admin option in the next release.

kind regards

[alexg]

OK, can you please tell me two things?

1. Does the problem persist if you switch to a standard theme such as twenty seventeen?

2. Are there any errors in your JavaScript console? You can open up the console by hitting the F12 key.

Unfortunately there is no separate shortcode for the timer, it is bundled together with the claim function.

[alexg]

Thanks I will investigate.

[Author]

Posts