I reply to all queries on the forums and via email, once per day, Monday to Friday (not weekends).

If you are new here, please see some information on how to ask for support. Thank you!

Hot wallet balance not updating

dashed-slug.net Forums General discussion Hot wallet balance not updating

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #11469
    Anonymous
    Inactive

    Hello again, Love the plugins. Have a question about the cold wallet section.
    Is there a way to force the plugin to recheck the hot wallet balance when it does not match actual wallet balance?
    This does not really matter for functionality as I keep record of the wallet via other means. Just curious.

    Thank you

    #11471
    alexg
    Keymaster

    Hello,

    Normally the hot wallet balance should be updated after 30 seconds at most. The same hot wallet balance should be shown in the Cold Storage screens and in the Adapters list screen.

    For coin with ticker symbol XYZ, the hot wallet balance is cached for 30 seconds in the transient wallets_get_balance_XYZ. So, for bitcoin, the hot wallet balance will be cached in wallets_get_balance_BTC.

    After 30 seconds the transient will expire, and the new value will be read from the wallet and shown again.

    Unfortunately some server cache plugins, when not correctly configured, fail to expire transients as specified by the WordPress API. To verify that this is the problem with your setup, go enable the checkbox at WalletsFrontend SettingsDisable transients (debug) and hit “Save Changes”. This issue will cause problems with other plugins as well.

    Do this only to verify that this is the problem. Your site will become slow if you leave this setting on.

    After you verify that the problem is related to your caching plugin, check its settings again. For example, if you’ve enabled memcached support but you don’t have a memcached server, this could happen. I’m sorry but I don’t know under which specific conditions caching plugins do this. I only know that, when you delegate transients to caching plugins, then WordPress is no longer responsible for expiring transients, but delegates this to whatever mechanism you’re using.

    I’ve tried to address this issue better in the upcoming wallets6 plugin.

    with regards

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.