[alexg]

In version 0.7.0-beta of the Exchange extension, if you choose to use the new static templates, you can specify an initial timeframe for your chart. For example: [wallets_exchange_chart template="static" market="BTC_LTC" timeframe="1h"]. This will not work with the previous dynamic template (default).

Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/ and the accompanying documentation for more examples of what shortcodes you can use.

[alexg]

In version 0.7.0-beta of the Exchange extension, if you choose to use the new static shortcodes, then you can specify a market. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/ and have a look at the accompanying documentation for examples on how to use the shortcodes.

[alexg]

In version 0.7.0-beta of the Exchange extension, if you choose to use the new static shortcodes, then you can specify a market. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/ and have a look at the accompanying documentation for examples on how to use the shortcodes.

[alexg]

Please see here.

[alexg]

In version 0.7.0-beta of the Exchange extension, there are now static templates for the shortcodes.

Static shortcodes are rendered once, server-side, and they require a market attribute, because they are only rendered for that one market.

There is detailed information in the documentation on how to use these. Please also see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

In version 0.7.0-beta of the Exchange extension, the above CSS rule has been included. This should cause the last column of the table to expand to the remaining available size, for most themes. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

In version 0.7.0-beta of the Exchange extension, there is now a new shortcode [wallets_exchange_market template="horizontal-dropdown"]. The equivalent, if you choose to use the new static templates, is[wallets_exchange_market template=”horizontal-static”]`. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

In version 0.7.0-beta of the Exchange extension, these rounding errors have been eliminated by rounding available amounts down (floor function) to the closest satoshi, rather than simply rounding to the closest value. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

In version 0.7.0-beta of the Exchange extension, the [wallets_exchange_market] table allows the user to select a market by clicking anywhere on the table row, and the radio buttons have been removed. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

In version 0.7.0-beta of the Exchange extension, the orderbook is available even for non-logged-in users. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

In version 0.7.0-beta of the Exchange extension, the table headers now show coin symbols where appropriate to visually aid new users. Please see the full release notes here: https://www.dashed-slug.net/static-exchange-templates/

[alexg]

Hello,

I have modified version 3 of the JSON API in plugin version 4.2.1. The __wallets_user_id argument is now ignored. If you specify an API key in your calls, the effective user whose data is returned, is always the user who corresponds to the given API key.

with regards

[alexg]

Dropping the user_id requirement is something that I would like to do, as it is the best solution. I hadn’t found an efficient way to do this yet but it is the correct solution.

As this will go into JSON API 4, I cannot provide an estimate. As a general rule I only provide estimates for defects, not new features, since it is impossible to estimate how long things take.

I will look into how to eliminate the requirement for a user_id argument and let you know.

with regards

[alexg]

Hi Phillip,

Looking into this a bit further:

The get_nonces API call can by design only be performed by a logged-in user (i.e. with the cookies method, going through wp-login.php). This is typically done by a browser but does not have to be.

My original intention was to be able to display the user_id and api_key with the [wallets_api_key] shortcode, so that the user is then able to enter it into some other application and grant access. But the user must first login to the website to obtain this information.

I am curious, what your login workflow would be? If the user can already login, what’s the use of having a user_id and key? What type of credential would the user provide to your application via your UI?

[alexg]

It would be hard to achieve what you ask with knockout templates, this is why I suggested using a standard HTML form and some simple JavaScript.

The JSON API call, using jQuery would be:

$.ajax({
	dataType: 'json',
	data: {
		'__wallets_apiversion' : 3
		'__wallets_action' : 'do_withdraw',
		'__wallets_withdraw_address' : address,
		'__wallets_symbol' : symbol,
		'__wallets_withdraw_amount' : amount,
		'__wallets_withdraw_comment' : comment,
		'__wallets_withdraw_extra' : extra,
		'_wpnonce' : wp.wallets.viewModels.wallets.nonces()['do_withdraw']
	},
	success: function( response ) {

		$( form ).trigger( 'wallets_do_withdraw', [
			response,
			symbol,
			amount,
			address,
			comment,
			extra
		] );

	error: function() {
		alert( 'Withdrawal not submitted' );
	}
});

Just make sure to attach this to whatever button your form has, and pass the variables in from the form.

Hope this is a bit more clear. The rest is just standard html/javascript.

with regards

[Author]

Posts