Forum Replies Created
-
Posts
-
Ah yes, this is a bug that was fixed in the latest version. Sorry about that.
Either update to the latest version, or add a passphrase to your wallet.
Ideally you should do both.
kind regards
Thanks coinstar for your input.
Since the OP is testing in a VM, it is unlikely that sendmail would be installed AND correctly set up. As you know setting up an email server is a lot of hard work. This is why I suggested the plugin solution.
As for emails going to the spam folder, this can be easily solved for testing purposes, if you just add the email to your contacts in your webmail solution.
On an actual live setup you would not have to do any of this, of course.
Hello,
If you are not getting emails this is not an issue with the plugin, but with your OS setup. Unless you have set up sendmail on a system, emails will not work.
Since you are testing in a VM, it makes sense that this would not be set up, while on an actual live server provided by a web host, emails would work.
The easiest workaround I can think of is to forward emails through a gmail account. You can setup a plugin such as this one: https://wordpress.org/plugins/wp-mail-smtp/
It’s what I use in my development environment.
Once you get emails working, let me know what error you get with your withdrawals.
kind regards
Hello,
Which adapter are you using? Fees are determined by the coin adapter. The fees are intended to cover the blockchain fees plus any more fees that you may want to charge. The actual fees paid on the blockchain are specified in your actual wallet if you are using a stand-alone wallet, or by your cloud wallet if you are using one of the cloud wallets. The fees you specify in the coin adapter settings should at least cover your actual fees.
When you attempt to send a withdrawal, it must be validated by the user and admin by default. When you visit the transactions screen, in what state is your withdrawal? If it is in a “failed” state, then the user will have received an email with an error message that will let you know what the problem was.
As for internal transfers, these are nearly instantaneous but not quite. First they must be user-verified over email by default. Then they are executed in batches on the next cron runs. You can control how often cron runs and how large a batch of transactions it processes each time.
Let me know which adapter you’re using and what error you get with your withdrawal.
kind regards,
AlexIf you have installed the CoinPayments adapter then you will need to enable some coins both in your CoinPayments account and in the CoinPayments adapter settings in your admin settings. Follow the installation guide carefully, where this and some other stuff is mentioned.
Hello,
Did you check the troubleshooting section? Most likely you have not configured the capabilities correctly.
Check the troubleshooting section in the manual and let me know if this is the problem.
I am aware of the JavaScript warning you mentioned. It has nothing to do with this, but it will be solved soon.
kind regards
The situation is as follows:
You can immediately use any of the RPC adapters that you can find on the download section of this site, so these few coins are covered. You can connect to the following wallets: LTC, DOGE, FTC, GridCoin, GoldCoin. You can also easily modify the Litecoin adapter to connect to other coins based on the same technology. This requires that you maintain servers that run these wallets.
Alternatively you can use a cloud wallet which requires little to no maintenance. For maximum coin coverage, your best bet right now is to use the CoinPayments adapter instead. The adapter supports any coins that CoinPayments supports, so the list is dynamic. For a list of coins used by CoinPayments, refer to this list: https://www.coinpayments.net/supported-coins
The fixes have now been deployed.
If you like you can check again after updating both Bitcoin and Altcoin Wallets (the main plugin) and the CoinAdapter extension to their latest versions, 2.11.1 and 0.5.1-beta, respectively.
regards
AlexHi again,
Apologies for the long delay. I was very busy these days. This is indeed an important issue, thanks for reporting.
I have now fixed the problems with the fees. The changes will be in the next release. Hopefully this will be out today.
kind regards
Hi.
No, I have not got around to looking at this yet. It is in my backlog.
When I do have news I will post here.
What shortcode are you using? For Bitcoin you would write something like
[wallets_faucet symbol=”BTC” captcha=”recaptcha”]
Is the adapter status “responding”? Check in Wallets -> Adapters.
Thanks for reporting, I’ll fix that.
In the meantime you can upgrade to PHP 5.5 or later to solve the issue if you’re interested.
You do not need to upload the documentation. The documentation is there so you can read it. Just open up
index.htmlin your browser.Yes I’ve been meaning to fix this but I didn’t find the time yet.
In the meantime, you can download the bundle from the downloads section. It contains a copy of the PHPdocs.
regards
Yes,
I have not yet found the time to create a membership extension to the plugin, so I can accept cryptocurrencies automatically. This is in my plans right after finishing a shapeshift extension that I’m currently working on.
You could send me Bitcoin at the address given in the plugin’s readme, but as the fees are currently high, you might prefer to send me the equivalent of $9.95 via Doge coin at: DASHEDj9RrTzQoJvP3WC48cFzUerKcYxHc
Send me the txid and the email address you used to sign up, at info@dashed-slug.net. I will then activate your membership manually.
Thank you for your interest in becoming a member.
kind regards
Alex
