Forum Replies Created
-
Posts
-
Thank you so much for reporting this and for taking the time to debug the root cause!
You are of course correct, when a site uses SSL (as it should, nowadays), the correct API endpoint is
secure-api.solvemedia,com. If it does not, then it’sapi.solvemedia.com. Source: https://solvemedia.zendesk.com/hc/en-us/articles/203648204-Implementing-Over-HTTPSThis change is implemented in the faucet version 1.1.2.
Again thanks, I appreciate it.
regards,
AlexI have found why the captcha is not shown.
In the file /wallets-faucet/includes/claim.php i have canged
//api.solvemedia.com/papi/…. to
//api-secure.solvemedia.com/papi/….now it works
Hi, can you please check the following:
1. You can only set a faucet owner to be a user with the
manage_walletscapability. Check that you have at least one user with that capability.2. Once you do successfully set a user, you will not be able to claim funds from the faucet while logged in as that user. You will need to setup another account to test the faucet.
Also, are you on a multisite installation?
regards,
AlexOK I had a look and I will post a short and a long explanation:
Short version:
You can delete the filewallets-faucet/includes/third-party/class-tgm-plugin-activation.phpand 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,
AlexThanks 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,
AlexThe 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,
AlexHello,
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.
From time to time I update the litecoin and other adapters. Simply remove the
ds-update.phpfile before redistributing your plugin extension.Start by looking here: https://www.dashed-slug.net/developers-coin-adapters-api/
Also, keep in mind that after editing the
.conffile you should restart your daemon for the changes to take effect.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.
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,
AlexWhat 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.
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,
AlexI 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
