[alexg]

OK. Did you check the server time or only the timezone setting?

The plugin stores the GMT time, then uses the current timezone to offset the time before displaying it.

You would only see a change in new transactions, not in the old ones. Did you attempt a new “move” transfer?

[alexg]

Hello,

The created_time field in deposit transactions coming from RPC API wallets comes from the wallet itself. It is displayed using the default WordPress timezone.

Instead, the created_time for internal transfers (moves) has to come from WordPress.

First set the UTC time correctly on your WordPress server. Then, visit the WordPress admin in Settings -> General -> Timezone and set the timezone correctly. Check that the dates that WordPress reports make sense in your location. Then, check the Tranactions list in admin and make sure that the created time for new transactions is displayed correctly.

The transaction times, when displayed in the frontend are rendered with the timezone of the user’s browser, so you can’t control that.

with regards

[alexg]

Hello,

You can get the current market using JavaScript with wp.wallets.viewModels.walletsExchange.selectedMarket().

I haven’t added a way to change the ordering of coins, I will do so in a future version.

with regards

[alexg]

Thank you. So you’re not using memcached, WP Super Cache, W3 Total Cache, etc…

[alexg]

Hello,

Could you please reduce the size of your screenshot? The maximum post size is half a megabyte. Or upload the screenshot somewhere else?

Also, please check the status of the adapters, under Wallets -> Adapters -> Status, as this might be relevant.

And make sure that your user has all the right capabilities under Wallets -> Capabilities (give all caps except for manage_wallets).

[alexg]

@tanger Thank you so much for your feedback. Can I please ask what type of server-side cache you’re running? I have been trying to figure out why transients do not expire for some users for several months now.

All I know up to know is that when backed by the MySQL WordPress options table, the transients always expire correctly. But with some more advanced caching solutions there can be cases where the WordPress transients API does not behave as expected.

As a sidenote, it is also possible to clear transients using WP-Optimize, but clearing the transients manually is not a complete solution. This is why I want to find the root cause of this issue.

[alexg]

Hello,

Since you changed server, your server’s IP address is now different.

The RPC API of this type of wallets returns 403 when an incoming conection request does not pass through the wallet’s IP filter.

Go to your wallet’s .conf file, and edit the rpcallowip line to match your new IP. That’s all.

with regards

[alexg]

Hello,

I am not able to reproduce the warning “Failed to parse SourceMap” in Chrome or Chromium, but I wouldn’t worry about it. You only need map files if you are interested in debugging the JavaScript libraries. You could try and delete these two map files to hide the warning.

You also have some JavaScript errors in your console. They do not look like they come from one of the dashed-slug plugins but the errors may interfere with the UI. If you see any problems with the UI, perhaps you should track this error down.

with regards

[alexg]

Hello,

The forum is a great place to start learning about the plugin!

The Tip the Author extension does not really have integration with Buddypress. It cannot be displayed next to comments, but it can be associated with any post type. So any type of article, post, etc

The Tip the Author extension has special support for the DW Question and Answer plugin. This is a question/answer plugin that lets you create sites similar to StackExchange. Perhaps this is closer to what you have in mind?

with regards

P.S. I have moved your post to the forum for Tip the Author from the general discussion.

[alexg]

I see it as well. Thanks for noticing!

I will make a note to fix this in one of the next releases to improve performance.

with regards

[alexg]

Hello,

You can always override the icon for any coin, using a filter.

To specify the URL to an icon, please see the code in the documentation under Frontend -> UIs -> Coin Icon for an example of how to use the wallets_coin_icon_url_XYZ filter.

with regards

[alexg]

@tanger Hello, the screenshot you posted shows that the user only has about $1.00 of available balance. The rest of the balance is locked up either in another pending transaction, or an open order on the exchange. Make sure to cancel any other pending transactions from Wallets -> Transactions and any open orders in the exchange, then try again. Most probably you have already attempted one withdrawal and it never got executed. Pending transactions get cancelled by default after one day, you can change this behavior in the Cron job settings with the “Cancel old unconfirmed/pending transactions” option.

[alexg]

Balances cannot be adjusted generally, they are only the sum of the transactions that affect a user.

So to adjust a balance, send fiat to that user.

There is however the possibility to use the Airdrop extension to add balance to a group of users. This can be based on user roles (so you could give some fiat to the admin for example).

If you want the user to pay the admin, the user must initiate an internal transfer with [wallets_move].

If you want to write your own code, you can also initiate transactions via the JSON API (e.g. from the browser) or via the PHP API (from your theme or another plugin).

Let me know if this answers your question. If not, what is your use case?

with regards

[alexg]

Thank you for taking the time to post this info!

That makes sense, it’s probably best to run a pruned node in most cases, as it saves on server resources.

[alexg]

My apologies, I thought you were trying to use knockout because I saw some input field names that match the observables. My mistake.

The next step would be to use JavaScript to call the JSON API when the form is submitted. That’s it!

[Author]

Posts