Acato

Hi @perryrylance

That is really nice to hear!

Hi @sagirika

Thank you for using our plugin!

Just to be clear: with the “cached routes list” you mean the Endpoint API Caches? If you do not see any records there it almost sounds as if the must use plugin isn’t installed (correctly). Can you please check the /wp-content/mu-plugins directory and see if there is a file called wp-rest-cache.php?

Hi @workforpizza

Thank you for using our plugin!

You can indeed manipulate these headers using filters. There are two filters you can use: wp_rest_cache/cache_headers and/or wp_rest_cache/cache_header. Examples of how to use them:

Adding new headers:

function wprc_manipulate_cache_headers( $headers, $request_uri ) {
    // manipulate the headers here, for example add a Access-Control-Allow-Headers header:
    $headers['Access-Control-Allow-Headers'] = 'X-Requested-With';

    return $headers;
}
add_filter( 'wp_rest_cache/cache_headers', 'wprc_manipulate_cache_headers', 10, 2 );

Manipulate an existing header (can in fact also be done with the wp_rest_cache/cache_headers, but just as a different example):

function wprc_manipulate_existing_cache_header( $header_value, $header_key, $request_uri ) {
    if( 'Access-Control-Expose-Headers' === $header_key ) {
        $header_value = 'X-WP-Total';
    }
    return $header_value;
}
add_filter( 'wp_rest_cache/cache_header', 'wprc_manipulate_existing_cache_header', 10, 3 );

Please keep in mind that you should flush the cache in order for these filters to have any effect.

Let us know if this solved your issue or if you need any extra help!

Hi @redcastor

Thank you for using our plugin!

In order to solve your issue as good as possible, I would like to know a little bit more about the background of your question. Why exactly don’t you want it to be cached?

These caches are flushed automatically whenever the item is edited. So there should be no problem to cache it. What (kind of) data is added to the object at what point that it should not be cached?

Hi @machi

First of all: sorry for the late reply! Somehow we did not receive an email when you placed your question.

About your question: it has nothing to do with a v3 API, but with the fact that ACF adds its own endpoints (which is apparently on version 3). At this moment you can register the endpoint for caching (see our Frequently Asked Question section “Can I register my own endpoint for caching?”), unfortunately these caches will not be automatically flushed. However, we do have plans to integrate ACF endpoint caching in our plugin (we also use them a lot) and will then make sure they are flushed automatically.

Hi @jenilk

I finally have found the time to investigate this issue more thoroughly and have found the cause of the issue when memcached is activated. It has to do with the default expiration setting of 1 year. When memcached is activated, the PHP Memcached class is used. Just like the set_transient() function of WordPress it has an expiration setting.

However for memcached there is a small difference which can make a huge impact: whenever an expiration of more than or equeal to 30 days is used, it is no longer treated as seconds-from-now, but in stead as a unix timestamp. Since 1 year in seconds is a unix timestamp which translates to Fri, 01 Jan 1971 05:48:46, the cache is immediately expired.

So a quick fix would be to set your cache timeout lower than 30 days. Meanwhile we are searching for a better fix, that will allow you to have a cache timeout of more than 30 days.

Hi @jenilk

Unfortunately at this point I am not sure what is causing the issue. It is probably related to the issue I got when I unchecked that setting, but I won’t know for sure until I investigate this more thoroughly.

To help me debugging this issue, could you please tell me which cache types you enable in W3 Total Cache? (i.e. Page Cache, OpCode Cache, …) And potentially which Cache Method (Disk / Opcode / Memcached / Redis / ..)

I am sorry I can not help you at this point, but we will investigate and try to solve this as soon as possible.

Well that was exactly the issue I was getting when I installed W3TC and unchecked the setting ‘Store transients in database’.

The reason you are getting the status Cache is expired or flushed is because the transient can no longer be retrieved. So somehow the transients aren’t stored correctly.

Did you uncheck the setting? If not, than there must be something else that is interfering with the transients.