Forum Replies Created
-
AuthorPosts
-
August 14, 2019 at 2:05 pm in reply to: Include USD Converted Value of Coin in User email notification #6724
alexg
KeymasterHello,
Apologies for the late reply, I saw your other post at https://www.dashed-slug.net/forums/topic/include-usd-converted-value-of-coin-in-user-email-notification/ but it seems like you deleted it.
In any case, what you are asking is not possible at the moment. I might be able to add this into the next release. It will then be possible to show the equivalent value in whatever currency the user has selected to see as “fiat currency”.
I will notify you again on this thread when this is out.
with regards
alexg
KeymasterHello,
The menu by design does not offer any links. It is simply another way to display the balances in a more compact way.
The expected behavior is what you describe for BTC. There should not be any link on the first coin. I am not sure why on the first coin you get a different URL. In any case, the menu item is not built to have links.
with regards
alexg
KeymasterIn version
1.0.2
of the coin adapter, if the transfer time is not reported by the wallet RPC API, then the time that the transfer was discovered is used as creation time for the transaction. This should be OK in most cases.with regards
alexg
KeymasterThe log warning coming from the Monero Coin Adapter extension is now eliminated in version 1.0.2.
alexg
KeymasterHello,
First of all you can edit the email test in the admin page: “Wallets” -> “Notifications”.
Without knowing which wallet you are connecting to it is not possible to know exactly why the transaction date is not set.
The adapter uses the “timestamp” field from the response to the RPC command
get_transfers
: https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#get_transfersI will release a patch to the coin adapter soon with a workaround to the problem. I will notify you again on this thread.
with regards
alexg
KeymasterThanks for reporting this. I will have a look soon and will keep you updated.
with regards
alexg
KeymasterThanks for reporting this. I will have a look soon and will keep you updated.
with regards
alexg
KeymasterThanks for reporting this. I will have a look soon and will keep you updated.
with regards
alexg
KeymasterAh, OK
1440
is the maximum allowed in the plugin.The coin adapter hook looks good.
In any case, I will check with the CRW wallet to see if I can reproduce the problem. I will let you know what I find.
with regards
alexg
KeymasterHello,
It sounds like you did everything correctly except for one thing:
The deposit addresses already generated for your users are those of the old CP account. Whenever you switch adapters, please follow the instructions in the FAQ under “I want to replace an adapter with another one.” Namely, you need to click on “Renew deposit addresses” for each coin that is now handled by a new wallet.
with regards
alexg
KeymasterHello,
Yes, you are right, this should be possible. I will fix this for the next patch release of Tip the Author. I will notify you here when this is out.
with regards
August 2, 2019 at 9:31 am in reply to: Possible to change the plugin label for woo commerce payment options #6689alexg
KeymasterHello,
Yes, it is possible to change the name of the payment gateway.
Please go to “WooCommerce” -> “Settings” -> “Payment” -> “Bitcoin and Altcoin Wallets” and change the “Title” field.
with regards
August 2, 2019 at 9:26 am in reply to: Payment error: Selected cryptocurrency is not enabled for payment #6688alexg
Keymaster@bigblue I see now, thank you, you are correct. This is the same bug you reported back then.
alexg
KeymasterHello,
Where did you see a max value of 1440?
In Bitcoin core the maximum wallet timeout is 100000000 seconds, or about 3 years. Is your wallet different?
Please keep me posted about whether your fix works.
If you could tell me which wallet you are connecting to, perhaps I could test with that wallet.
with regards
August 1, 2019 at 8:54 am in reply to: Payment error: Selected cryptocurrency is not enabled for payment #6678alexg
KeymasterI have fixed the issue in version
2.1.2
. The bug was introduced in2.1.0
but went undetected until now. Thanks again for spotting this issue and apologies for the trouble. -
AuthorPosts