[alexg]

OK I had a look and I will post a short and a long explanation:

Short version:
You can delete the file wallets-faucet/includes/third-party/class-tgm-plugin-activation.php and your immediate problem should go away.

Long version:
TGMPA is a very common library for tracking dependencies among wordpress themes and plugins. For this reason, many authors use it. The version that I have included into the faucet plugin, TGMPA 2.6.1, is careful enough to not re-declare itself if it is already declared. The error you are getting is triggered from your meta4delicious theme, which I assume has an older version of TGMPA, that did not do that check.

I would recommend that you let the author of that theme know about this, so they can update to a more recent TGMPA version.

Let me know if deleting the file fixes your problem.

regards,
Alex

[alexg]

Thanks for reporting this.

I will fix it and release a new faucet version soon.

I will let you know when the fix is out.

regards,
Alex

[alexg]

The plugin does not call any of those methods.

There is no premium version of the plugin, but there are some premium extensions to it.

All is explained on the homepage https://www.dashed-slug.net

regards,
Alex

[alexg]

Remember to set sane values to transaction fees on plugin activation.

[alexg]

Hello,

And thanks for your kind words.

Yes, pretty much. If your coin is a clone of Bitcoin that retains most of its JSON-RPC API intact, then it should be just a matter of replacing strings. You can start from the litecoin adapter which I consider the reference implementation.

Litecoin RPC Adapter extension

From time to time I update the litecoin and other adapters. Simply remove the ds-update.php file before redistributing your plugin extension.

Start by looking here: https://www.dashed-slug.net/developers-coin-adapters-api/

[alexg]

mumiea, what have you tried? Did you check your firewall on the VPS site?

[alexg]

Also, keep in mind that after editing the .conf file you should restart your daemon for the changes to take effect.

[alexg]

While it is true that VPSs don’t allow you to constantly use 100% CPU, this should not be a problem, as you’re not supposed to CPU-mine anything. Not only is CPU mining bitcoins terribly inefficient as of 2017, but it has nothing to do with maintaining a wallet. It is true that while synchronizing the blockchain the wallet uses the CPU a bit more as it is confirming blocks, but after it synchronizes, CPU usage should be minimal.

If the box is still showing then that means that for whatever reason the wallet is still not connecting. Have a look at the adapters page, and specifically at the status column for your bitcoin adapter. There should be more information about why the plugin is not connecting.

[alexg]

Hello,

The WooCommerce payment gateway settings do not appear under the Wallets tab, rather they appear together with the other payment gateways in WooCommerce → Settings → Checkout → Bitcoin and Altcoin Wallets as described in the instructions.

If you find this path hard to remember, you can go to Plugins and find the WooCommerce Cryptocurrency Payment Gateway extension. It will have a link to “Settings” under the plugin name.

regards,
Alex

[alexg]

What exactly are you trying to achieve? The faucet is broken up into a number of shortcodes so that you can insert those into your own layout. Additionally, you can use CSS to style these parts. You will not be able to easily control the captchas themselves because they are in IFRAMEs, but this is not a limitation of this plugin. Other than that, you should be able to control the layout by arranging the shortcodes and with CSS.

[alexg]

Hello,

I have implemented the proportional fees request in wallets version 2.4.5 and you can set proportional fees throughout all coinpayments adapters in one setting in the latest adapter version 0.3.1-beta. Also, the 0.5% deposit fee incurred by the platform is now correctly reflected in the transactions table, as is the fixed coinpayments withdrawal fee, which is different for each coin.

0.3.1-beta should also fix the situation where coins were not being listed. Additionally, if there is an error while listing coins, you should be seeing a useful error message in your admin area. Try it in your staging area and let me know.

regards,
Alex

[alexg]

I removed the fees settings because they were getting too complicated. In a later version I will combine the fees into one setting that will be expressed as a percentage. I already have another request where several users are asking for fees to be expressed as a percentage of the transacted amount, so this will have to happen first.

Since you are running a WooCommerce site, you should be earning funds by selling products, not by setting fees on transactions. The fee is mainly to cover blockchain fees.

Like I said, this adapter is in beta so expect more changes soon.

regards,
Alex

[alexg]

The latest version 0.3.0-beta supports Ethereum as well as some other coins. See the release notes here:

Improvements to the CoinPayments cloud wallet adapter including Ethereum availability

[alexg]

1. The electrum adapter is now available at https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/electrum-bitcoin-rpc-adapter-extension/
2. The plugin uses blockchains for deposits and withdrawals. It maintains an internal ledger on the database to record transactions between users and to maintain user balances.

regards
Alex

[alexg]

Hi,

Since your question is about the bitcoin daemon and not the WordPress plugin, you might have more luck asking at channels related to the Bitcoin wallet, such as https://bitcoin.stackexchange.com or https://bitcointalk.org . Having said this, here’s a few things that come to mind:

You will probably want to install bitcoind as a service, not just run it from the command line. Most installation guides tell you how to do this for your system. Perhaps the installation process that you performed has already done this? It could well be that bitcoin is running. Try a bitcoin-cli getbalance and see if you get a number as a response. You can also check to see if the daemon is running with ps ax | grep bitcoind. To see if that port is open do netstat -a | grep 8332.

Let me know what you find.

regards,
Alex

[Author]

Posts