Forum Replies Created

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

    (@dashedslug)

    Thank you both @enochdavid and @001chareal for the additional info.

    I am not certain why this issue is happening and I am not able to reproduce the problem on my end. You have correctly enabled some coins and this is reflected in the backend, but the frontend does not show the coins.

    5. Please navigate to http://example.com/?__wallets_apiversion=3&__wallets_action=get_coins_info and show me what you see (first replace example.com with the actual domain of your site).

    6. Are you using WordPress multisite?

    7. It is likely that some server-side cache is misbehaving. If you’re using any type of caching mechanism, such as W3 Total Cache, WP Super Cache, memcached, etc, go to your cache plugin’s settings and clear the cache. Check again to see if the problem is resolved. Normally this shouldn’t happen, but it’s easy to check by clearing your cache.

    8. The latest version of the CoinPayments adapter, 1.1.0 includes many changes that are very recent. I have already received reports from people who are using the latest version successfully. But you can check the previous version too, 1.0.8. If the previous version works, then please let me know.

    That’s all I can think of for now. Please check the above, and let me know. I will investigate further, and if I have anything else to add I will post here again.

    with regards
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello David,

    Please tell me the following:

    1. Which instructions did you follow?

    2. Which coin adapters did you enable?

    3. Go to Wallets -> Adapters. Which adapters do you see?

    4. In that same screen, what does the “status” column read for these adapters?

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you Felty for the additional info.

    I am closing this thread since you managed to resolve the issue, but I will investigate.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello and thanks for your feedback.

    Normally, the plugin does the following, after activation:

    https://github.com/dashed-slug/wallets/blob/master/includes/caps.php#L65-L88

    This ensures that the admin has the manage_wallets capability, and that users who can edit posts get has_wallets and the other capabilities.

    Are you on a multisite install? If the plugin is network active, it would explain the issue. The manage_wallets capability is given to users who can manage the network.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    This is by design. There is not always a 1-to-1 correlation between wallet addresses and users. When you perform internal transfers there should be nothing happening in the wallet, as these transactions are only on your WordPress DB. There are no actual blockchain transactions.

    If you withdraw the funds via the wallet, whether it’s block.io or some other wallet, this will not be reflected in the plugin. Instead, use the plugin’s withdraw feature.

    (My apologies for the late reply. I am not sure why but I missed the notification for your post)

    with regards

    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Version 4.3.0 has a fix for the bug with QR codes in static deposit UIs.

    Additionally, it is now possible to set a site-wide default coin (Frontend Settings) or to set the default coin for a page or post (via a new meta box).

    Thank you for finding and reporting this issue.

    with regards
    Alex

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    The way to do display a particular coin’s deposit info is with a static template, i.e.

    [wallets_deposit template="static" symbol="ETH"]

    However there is currently a bug where this static shortcode does not display a QR code for the correct coin. I intend to fix this as soon as possible with the next patch release.

    I will notify you here when the bug is fixed.

    Additionally, the next version will let you set the initial default coin for any non-static templates. You will be able to set a coin default either site-wide, or per page. This feature has already been developed and tested. It will be released when the bug with the static template is fixed.

    with regards

    • This reply was modified 7 years, 1 month ago by dashed-slug.net. Reason: added more info about default coin selection
    Plugin Author dashed-slug.net

    (@dashedslug)

    Not at all, glad it worked!

    Plugin Author dashed-slug.net

    (@dashedslug)

    Apologies, disregard my previous comments. I just now noticed the problem in your screenshot:

    You have used dashes ‘-‘ where you should be using underscores ‘_’.

    So, for example, use [wallets_deposit] instead of [wallets-deposit].

    This should solve your issue.

    If afterwards you encounter some other issue, please open a new thread.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello and thank you for posting the debug info. Your installation looks pretty standard, no surprises there.

    First of all, to see why it’s not a good idea to edit the code, see the FAQ under “I want to do changes to the plugin’s code. Where can I find X function/variable/command/etc?”

    Let’s first identify the problem. If there is a bug in the code, I will fix it, but it’s unlikely that this part of the code has any errors, since it’s old and well-tested. Most probably this is a configuration problem. In any case, the shortcodes are defined here if you want to have a look: https://github.com/dashed-slug/wallets/blob/4.2.1/includes/shortcodes.php

    1. It is normal to get the error you posted when the plugin is deactivated (Unexpected token < in JSON). The frontend normally queries the JSON API. This error means that the JSON API calls no longer return data, but instead return your page’s HTML, which can’t be parsed as JSON. You can’t expect the plugin’s API to continue working when you deactivate the plugin. If you keep the plugin activated you will not get this error.

    2. Check your JavaScript console for any errors. These would prevent the shortcodes from displaying.

    3. In the screenshot you show me, the shortcodes appear as if the plugin is deactivated. It is possible that your page is cached on the server side. (Think W3 Total Cache, WP Super Cache, etc.) Clear any server side caches to see if this is the problem. Clearing your browser cache might also help, so give it a try.

    Please let me know if you tried all of the above and you continue to face problems.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    There need to be some coin adapters that are enabled and with a status of “responding”. Please tell me the following:

    1. Which coin adapter or adapters did you install?

    2. Which instructions did you follow?

    3. Got to WalletsAdapters. Check the Adapter status next to your coin adapters. It should read Responding. Do you see something else?

    4. While logged in to your site, go to https://screenhubonline.com/?__wallets_apiversion=3&__wallets_action=get_coins_info Do you see a list of coins?

    Plugin Author dashed-slug.net

    (@dashedslug)

    After investigating, it turns out this issue caused internal transactions to not fail when there is not enough available balance. Instead, they remained in pending state. This bug was introduced in 4.0.0. I have provided a fix for this issue in version 4.0.5.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thanks for the clarification.

    If you get a message saying that the cron job has not run, then that is the problem.

    Before, the plugin would consider that the cron jobs have run, if they had started. Now, they are considered to have run if they have finished. This means that probably the process crashes mid-way for some reason.

    A couple of things you could check:

    1. Run the cron job manually by clicking on the link provided in the admin screen. Do you get { result: "success" }? Do the transactions get processed then?

    2. To diagnose if the jobs indeed crash mid-way, you could enable “Verbose log output” in the cron job settings. Then, the log output in wp-content/debug.log will show if execution is running out of memory, or after which task it fails. If you like, post here or email me the log output and I can look at it.

    Plugin Author dashed-slug.net

    (@dashedslug)

    Hello,

    Apologies for the delay.

    1. To be clear, do internal transfers work only for users who were created by an admin, but not for users who signed up to your site on their own?

    2. Also, have you checked the user capabilities?

    Please let me know. Thank you.

    with regards

    Plugin Author dashed-slug.net

    (@dashedslug)

    Thank you Shadi for taking the time to write this stellar review! I appreciate it very much.

    (To be clear, it is not possible for me to implement all user requests within days or hours, as you say. I do not believe that this would be possible, as some requests are ambitious and I am only one person. However I do try to prioritize debugging, and I do generally try to implement user-requested features if possible.)

    Thanks again!

Viewing 15 replies - 166 through 180 (of 492 total)