Forum Replies Created

Viewing 15 replies - 91 through 105 (of 492 total)
  • Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Yes.

    Using the Fiat Coin Adapter extension to the plugin, it is possible for an admin to process user fiat deposits and withdrawals via bank transfer. Therefore users who have a fiat currency balance, can use the [wallets_move] shortcode to transfer fiat currencies to other users.

    Additionally, through the CoinPayments adapter extension, it is possible for users to deposit cryptocurrency stable balances for stablecoins such as USDT, TUSD, etc. These can also be transferred between users.

    It is not possible to deposit or withdraw fiat currencies via credit cards or other means, unless if you develop your own solution for this.

    Hope this helps. Please let me know here if you have any further questions on this topic. (Or if you have a different question about the plugin and its extensions, please open a new thread.)

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    The coin that is selected by default is the one that you select in WalletsFrontend SettingsUI/display settingsDefault coin. This applies throughout your site.

    You can also override this selection in certain pages. In the page editor for any page, scroll to the bottom, and you will find a metabox titled “Bitcoin and Altcoin Wallets default coin”.

    On the frontend, the plugin applies your selection by running the following JavaScript code. I am mentioning this because you may provide additional logic, by binding to the wallets_ready bubbling event in the same way. https://github.com/dashed-slug/wallets/blob/5.0.2/assets/scripts/wallets-ko.js#L1022-L1029 You can get access to the wallets viewModel via wp.wallets.viewModels.wallets from any variable scope.

    Finally, if you were to use the static UIs (rather than dynamic ones), then you can pass the coin as an attribute, and the UI’s HTML will be rendered for that coin only (hence static). Static UIs are discussed in the accompanying documentation. For example: [wallets_balance] would show you a box with a dropdown, where you can select a coin and display its balance, but [wallets_balance template="static" coin="BTC"] would display the current user’s BTC balance only. It’s up to you to see if you find static templates more useful in your case.

    Hope this answers your question.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you very much!

    Plugin Author dashed-slug.net

    (@dashedslug)

    @chelspayne Hello, please check this relevant how to guide.

    If the above does not solve your issue or if you have any other questions please open a new thread. This thread has been closed.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    I see that your JSON API now responds with LTCT, therefore I am closing this thread. If you are experiencing any other issue, please open a new thread.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    The fix is now out in version 5.0.1 of the plugin.

    Plugin Author dashed-slug.net

    (@dashedslug)

    OK, add the permission, as described above, and you should be good to go.

    Plugin Author dashed-slug.net

    (@dashedslug)

    If you are using the CoinPayments adapter, did you follow the video or did you read the article? I ask because there’s something missing from the video.

    The article mentions that you should also set the get_callback_address permission to your CoinPayments API key. (See notice at the top of the article, or step #23 in the installation instructions)

    This is also mentioned in the troubleshooter I linked above and in the video’s comment section.

    Let me know if you’ve double checked your API key permissions.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    I assume that you have already checked this guide: https://www.dashed-slug.net/howto-debug-shortcodes-no-currencies-are-currently-enabled/

    I signed up as a user on your site, and visited this JSON-API endpoint:
    https://tradeexperts.org/?__wallets_apiversion=3&__wallets_action=get_coins_info

    The response was an empty JSON.

    The following observable is therefore also empty: wp.wallets.viewModels.wallets.coins()

    Which coin adapters are you using? What is the status of your coin adapters? Go to WalletsAdapters and let me know what you see please.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Are you referring to SourceMap errors? These are not really errors, they are warnings that are of no consequence. They simply say that a map file was not found for the minified assets. If you see some other error please post it here.

    Plugin Author dashed-slug.net

    (@dashedslug)

    OK thank you.

    I have performed an investigation and this is what I found:

    1. HTML comments are NOT minified in the body of your HTML. Therefore, the only issue that you are currently experiencing is the error message.

    2. The HTML output of the plugin is somehow modified, possibly by your web server. None of the plugins on your site is doing this, nor is it due to your theme. In particular, a <script> tag gets a hex id attached to it for some reason, so that it becomes <script type="86f6f906d8056800b06438e8-text/javascript">. If you know why this happens, please let me know, because I’m very curious.

    3. HTML comments are stripped from your HTML header (NOT body), hence this is why the plugin’s detection shows the error message. Again, none of your plugins or your theme appear to be doing this.

    I have never experienced anything like this before, so I’m not sure exactly why this happens. I can only conclude that there’s something in your webserver that alters the HTML head section.

    The minifier detector introduced in version 5.0.0 of the plugin shows a false positive in your case. You are seeing the error message even though there is no real problem.

    I am currently preparing a new patch release for the plugin, which will be out either today or tomorrow. In this patch, the error message will be shown only in the browser console, not as an alert. In retrospect, the alert box was a mistake.

    Since HTML comments are not minified in the body of your HTML, you will not experience any more issues related to this, once the new patch is out.

    I will notify you here when it is released.

    Thank you for providing access and assisting in this investigation.

    with regards,
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    OK, since you are certain that the problem persists after you have disabled ALL plugin, I can login to your site to investigate.

    You can send me details on how to login over email if you wish.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    This is a new feature in version 5.0.0 of the plugin. It’s meant to detect when HTML comments are stripped away by some optimizer / minifier.

    Some of the plugin’s UI templates use Knockout virtual elements. (For an example, see this line in the [wallets_balance template=”list”] shortcode.)

    Before version 5.0.0, some users would install the plugin and find out much later that some templates are not working properly, so I decided to be proactive and show an error message upfront.

    Usually HTML comments can be stripped away by WordPress performance-enhancing plugins, such as WP-Optimize. If this is done by a plugin, you will have an option available to turn it off. The option will be in that plugin’s settings.

    You say that you get the error even after deactivating ALL other plugins. In this case, it is possible that HTML minifying happens at a lower level, i.e. at the web server level. Both Apache and Nginx have modules that can do this.

    If you are unsure, ask your hosting provider about this. They must be able to let you know if they are using any HTML minifier, and they should be able to disable it for you.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Please show me the error so I can help.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    I’m glad you resolved the issue.

    The IPNs are retried by the CoinPayments platform for at least 10 times. You would only need to resend one, if auto-sending it had failed for 10 times already.

    I’m marking this issue as resolved, but you should check to see that your IPN endpoint is not cached by any server-side caches. This is unlikely to be the issue, as IPN messages are HTTP POST requests which are rarely cached if at all.

    Another thought is that maybe your site was down for a while, or the network was down.

    with regards

Viewing 15 replies - 91 through 105 (of 492 total)