[alexg]

In version 1.2.1 of the WooCommerce Payment Gateway extension there is an option to switch fee payments on/off.

This does NOT mean that the gateway can be used with multi-vendor plugins, since the cryptocurrency payment is sent to the one designated address, as discussed above.

kind regards

[alexg]

Hello,

Hope you are well!

Yes this should be possible, I will add this to the list 🙂

kind regards

[alexg]

For some public API endpoints there is a few-seconds cache based on transients. For example, if you check json-api.php you will see that some responses are cached for the amount of seconds specified by the wallets_exchange_memoize_seconds option.

When there is no object cache installed, WordPress falls back to storing the transients on the options table. If there is an object cache installed the transients are stored on that. This is not the first time I see someone with an object cache experience problems with transients not expiring. After a quick search on the web it seems this is caused by misconfiguration of the object cache, although I’m not sure.

To check, can you clear your W3 Total Cache, or memcached, or whatever it is you’re using? Does this refresh the output of the APIs?

You should also be aware that DB rows of transients do not necessarily get deleted just because they are expired. WordPress does some garbage collection but it is not perfect, so third-party solutions exist to clear expired transients from the DB to save space. In any case, the WordPress transients API should not return expired transients even if they exist on the DB, assuming this is where they are stored on your system.

I can always add a switch to disable cache, but we should at least have some idea of what is going on here. The question is why your transients are not expiring. For example, the transient that stores output of the get_market_summaries call is wallets_exchange_summaries and by default should be cached for 5 seconds.

Please do let me know if you find anything about this.

kind regards

[alexg]

Thanks, your DB version seems pretty standard.

I am still not sure how the enum column could cause this DB error, although I have searched the web and SO extensively.

Can you confirm that 1. the error still occurs and 2. that it gets resolved when the only change you do, is to change the collation on the column to Utf8_bin?

[alexg]

Thank you. This will be fixed.

The correct place to look up the available shortcodes is this webpage and the Frontend section of the documentation.

kind regards

[alexg]

Yes, I already thought about this.

The JSON API does indeed cache the data on WordPress transients, but only for a few seconds.

Normally transients are stored on the options table in the database, but if you have a solution such as memcached installed, the transients can be stored there.

Does clearing your server cache resolve your problem?

[alexg]

Thanks Alex, will do and let you know. You have an account inside the system, when I’m done you should have a look 🙂

[alexg]

Here’s some things that might help:

1. Make sure you have the WordPress debug log enabled so you know what files the system looks for in case it cannot find them. You might need to debug the path.

2. You can avoid hooking to the filter altogether, if you use the views_dir argument in your shortcode. This is implemented in 3.2.0 and is discussed in the documentation. It might allow you to do more tests quicker and easier.

3. It could be some issue with the file permissions. Make sure that your files are readable by your webserver and that their directories are scannable (execute permission).

4. You can, but you do not need the directory structure wallets/includes/views. Just call your directory anything, such as wallet_views.

[alexg]

Nope:

function my_wallets_views_dir_override( $dir ) {
return get_stylesheet_directory_uri() . ‘/wallets/include/views/’;
}
add_filter( ‘wallets_views_dir’, ‘my_wallets_views_dir_override’ );

I place list.php inside /wallets/includes/views/balance/ (in my child theme folder)

does not work ..

[alexg]

Cool, looking forward to it .. 🙂

[alexg]

I believe you were looking at an old version of the documentation. In the latest version 3.5.6 the paths are already up-to-date.

– wp-content/plugins/wallets/includes/views/balance/default.php
– wp-content/plugins/wallets/includes/views/move/default.php
– wp-content/plugins/wallets/includes/views/deposit/default.php
– wp-content/plugins/wallets/includes/views/withdraw/default.php
– wp-content/plugins/wallets/includes/views/transactions/default.php
– wp-content/plugins/wallets/includes/views/account_value/default.php

What is your question about the functions you posted?

[alexg]

Yes, market volume and other market info will be displayable soon. This has already been requested by others and makes a lot of sense.

kind regards

[alexg]

This sounds like it could be due to the calls being cached.

If so, I will fix this in the next patch.

Does the problem resolve if you clear your browser’s cache?

[alexg]

No, version 3.6.0 will be out in a few days.

[alexg]

public function shortcode( $atts, $content = ”, $tag ) {
$view = preg_replace( ‘/^wallets_/’, ”, $tag );

$atts = shortcode_atts(
array(
‘template’ => ‘default’,
‘views_dir’ => apply_filters( ‘wallets_views_dir’, __DIR__ . ‘/views’ ),
), $atts, “wallets_$view”
);

[Author]

Posts