[alexg]

Hello,

Please see under Fees in the Glossary section of the documentation for a detailed explanation about how fees work.

kind regards

[alexg]

This is now fixed in version 1.3.5 of the faucet extension.

regards

[alexg]

Hello,

I will have a look at this soon.

Thank you

[alexg]

Hello,

Yes, this has been requested again a few months back, I simply have not had the time to implement it. It is in my backlog.

Thanks

[alexg]

Hello,

No, actually variable substitution is not needed in the block explorer links.

You can enter the coin symbol in lowercase as part of the URI.

There are instructions on how to do this in the manual.

kind regards

[alexg]

Hi yes I am aware of the issue.

You can fix it on your site with some CSS until I address it.

kind regards

[alexg]

OK in that case you should enter the coin symbol in lowercase.

There is no variable for the coin. Enter one link pattern per coin.

[alexg]

Hello Philipp,

Block explorer links do not accept variables in the same way that email templates do.

your link would be something like https://chainz.cryptoid.info/XYZ/tx.dws?%s

Where XYZ would be your coin and %s is substituted with the TXID using the PHP sprintf function.

I can make it so that %2$s is lowercase TXID while %s or %1$s is the current uppercase value.

This will go into the next release.

regards

[alexg]

Yes, and I replied to you over email that I could not login.

Perhaps my email went to your spam folder?

[alexg]

Haha thanks.

It’s not magic. Simply a combination of good project management skills and lots of caffeine.

Glad it worked for you.

[alexg]

Thanks Philip,

With your help I believe I have identified the problem and will provide a fix on the next release.

best,
Alex

[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

[Author]

Posts