[alexg]

Hello,

Thank you for the very detailed description of this issue.

According to your IPN history, the IPN message did indeed arrive to your plugin instance.

Since the message did arrive, the only other reason why it would not appear in your transactions list would be if the deposit address was not bound to your user.

Can you please hit the following query into your SQL console?

SELECT
	*
FROM
	wpk4_wallets_adds a
WHERE
	symbol = 'LTCT' AND
	address = 'YOUR_DEPOSIT_ADDRESS'
ORDER BY
	created_time DESC;

Please replace YOUR_DEPOSIT_ADDRESS with the actual address you used for this transaction.

This will confirm whether this address is indeed bound to a user.

Please let me know what you find.

regards

[alexg]

Thank you. I will investigate.

[alexg]

I have improved the redirect mechanism in Faucet 1.3.0. Now it should redirect to whatever the referral link was but without the referral code.

regards

[alexg]

Hello Klaus,

As long as you can provide a coin adapter for your coin’s wallet, you should not have any problem to only offer a wallet for that coin to your users. You will have to disable the built-in Bitcoin core node adapter (uncheck the “Enabled” option in the adapter settings).

If your coin is a direct fork of Bitcoin then you can connect to a running instance of your wallet using the Multi-adapter extension. Please refer to the documentation section “Coin Adapter development” for instructions.

If your wallet is different then you will need to implement parts of the coin adapter by extending the abstract class Dashed_Slug_Wallets_Coin_Adapter. Inspect the file wp-content/plugins/wallets/includes/coin-adapter.php and pay special attention to the methods under “// Wallet API”. You should create a class that extends these methods to connect to your wallet and to provide information about your coin. There instructions are in the PHPdoc comments and I remain available to answer any questions you may have.

To issue an initial amount to your users perhaps it’s best if you let the users create wallets, then, when everything is set up correctly, simply send a transaction to all the user deposit addresses.

Hope this is helpful. Do let me know if you have more questions or if any of this was not clear.

kind regards
Alex

[alexg]

Hello,

Yes I already intend to add coinhive to the faucet, I simply haven’t found the time to do this yet. I also think it is a good fit for the project.

Thank you for your suggestion.

[alexg]

The JavaScript error should now be resolved in the latest version 3.1.0 released today.

[alexg]

Hello Mario,

Thanks for all the information you sent me.

I am not certain that these two problems are related. However, I believe I can include a quick fix about the JavaScript error in the next patch release of the plugin.

About the problem with the internal transfer:

When you enter a destination user in the [wallets_move] shortcode, the plugin attempts to interpret this as a WordPress login name, a user email, or user slug. I believe the user “Mario” that you have created is an entry in your membership plugin. It is very likely that this entry corresponds to a WordPress login name of “mario” in your WordPress records. Can you please do the following?

1. Try to send to user “mario” with lowercase (small “m”) and see what happens.

2. Go to your WordPress admin screen, and then to “Users” -> “All Users”, then find the user record and click on “Edit”. What is the entry under the “Username” entry? This is the WordPress login name of that user.

3. What happens if you attempt to send to the user’s email?

If there are any differences between the user name in the wordpress records and the records of your membership plugin, then this would be the cause of the problem you are facing.

Please let me know if you attempt these three things.

kind regards

[alexg]

Glad you found it useful!

[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

[Author]

Posts