Richard Korthuis

Hi @hirngesicht

WP REST Cache itself doesn’t talk to Redis directly — it stores everything through the WordPress Transients API (with a wp_rest_cache_ key prefix). The fact that your caches end up in Redis means you have an external object cache drop-in active (e.g. the Redis Object Cache plugin by Till Krüss, or similar), and that drop-in is what decides which Redis database is used.

Most Redis object cache drop-ins use a single Redis database for all of WordPress and expose a WP_REDIS_DATABASE constant (in wp-config.php) to choose which one — but only one. They don’t natively support routing a subset of transients to a different DB.

If you want WP REST Cache transients specifically in a separate Redis database, you’d need a custom/modified object cache drop-in that detects the wp_rest_cache_ key prefix (or the underlying _transient_wp_rest_cache_* option name) and opens a second Redis connection on a different DB index for those keys. That’s outside the scope of this plugin, but it’s the layer you’d need to customise.

Hi @djibs13

Thank you for using our plugin!

We just released a new version of our plugin, which should solve this warning.

Hi @elmalak

Thank you for using our plugin!

It is completely normal that you have a mu-plugin and a normal plugin. The mu-plugin is needed to hook into WordPress very early in order to serve the cache before other plugins are executed. What is not normal is that you say that the normal plugin is deactivated. Deactivating that plugin should remove the mu-plugin automatically. Without the normal plugin activated the mu-plugin will not do anything.

With regards to the versions: the normal plugin is the one that gets updated frequently, because that holds almost all the logic. The mu-plugin is rarely updated, since it’s functionality is limited to loading very early, so that is why that plugin is still at version 2021.3.0

Hi @kaldata

Thank you for using our plugin and sorry you are experiencing this issue.

There isn’t a fltler to disable this functionality in this version. We hadn’t considered this usage of the post meta, so we will be releasing a new version of our plugin soon which will introduce a filter, but this will be a filter to ENABLE this functionality. So when this new version is released everything will be working again as it did before the previous release, you won’t be needing to add a filter if you don’t want caches to be cleared on post meta update.

I will let you know once the new version is released.

Hi @papazetis

Thank you for using our plugin!

The reason this happens is because of how our plugin is set up. It hooks into the WordPress process really early (using a mu-plugin) to check if a cache is available for the current REST request. If so it returns the cache and quits the rest of WordPress process. So any actions done by plugins or other code (like for the permission_callback) isn’t executed anymore.

Now there are two possible solutions I see to your issue. One is to save the authorization header, like I described in my response here: https://ww.wp.xz.cn/support/topic/private-cache-for-rest-endpoints-with-a-authorization-header/#post-12813691

The other one is to hook into the filter wp_rest_cache/skip_caching and do your permission check there and have it return true if there is no permission (i.e. have it skip caching in this case and therefore returning the response as if no caching exists). Please keep in mind that using that filter would require you to do so from a mu-plugin which comes alfabetically before wp-rest-cache.php

Hi @hirngesicht

Yesterday we released a new version of our plugin, which includes this feature!

Hi @bizbergthemes

Thank you for using our plugin!

My solution would be to make use of the wp_rest_cache/skip_caching filter. This should however be used inside a mu-plugin which comes alphabetically before wp-rest-cache.php (This is because of the way our plugin works). If you use this filter and have it return true in your use case, our plugin will not return a cache record.

So if you were to create a file skip-balance-cache.php inside the wp-contents/mu-plugins directory with something like this it should probably work:

<?php
/**
 * Skip cache if the balance parameter is used.
 *
 * @param bool $skip True if cache should be skipped.
 * @return bool
 */
function wprc_skip_balance_cache( $skip ) {
    if ( isset ( $_GET['balance'] ) ) {
        $skip = true;
    }

    return $skip;
}

add_filter( 'wp_rest_cache/skip_caching', 'wprc_skip_balance_cache' );

N.B. I did not test this code, I just typed it.