Acato

Hi @adamhammad

We have just released a new verion of the plugin. We have added a GET-parameter you can use to skip caching. Simply add ?skip_cache=1 to you REST call.

Please let us know if this works for you!

Hi @adamhammad

Well creating a new (duplicate) endpoint doesn’t feel right.

After some consideration I think there are two possible solutions to this problem:

1. We add a check to see if the current user is authenticated and if so, do not use caching. But that would mean that all responses for authenticated users are no longer using caching. That doesn’t feel right either.

2. We can implement the option for you to use an extra parameter to tell the WP REST Cache plugin to skip caching. That way you can decide for each request if you want to use caching or not. So for admin users you would add an extra parameter to the REST call. Does that sound like an option to you?

Hi @djcelo

Thank you for your review!
Please let us know if we can be of any assistance, if you are missing functionalities or if you have any suggestions.

Hi @waldub

Thank you for using our plugin!

We just released a new version which should solve at least part of your problem (the fact the error doesn’t go away after you deleted your code).

I am however not sure why you ever got this error, at some point your filter function must have returned a string in stead of the array $allowed_endpoints. Could you please download the latest version of our plugin and retry?

Hi @adamhammad

We just released a new version of our plugin which now includes a function to programatically flush caches by endpoint. So for instance if you want to flush the caches for the endpoint /wp-json/wp/v2/pages you can do so like this:
\WP_Rest_Cache_Plugin\Includes\Caching\Caching::get_instance()->delete_cache_by_endpoint( '/wp-json/wp/v2/pages' );

This function accepts two extra parameters:
1. $strictness: This defines how strict you want the caches to match, you have three options for this:
\WP_Rest_Cache_Plugin\Includes\Caching\Caching::FLUSH_STRICT: Delete caches by an endpoint path matching only this exact same endpoint path (and query params).
\WP_Rest_Cache_Plugin\Includes\Caching\Caching::FLUSH_PARAMS: Delete caches by an endpoint path matching the exact same endpoint path with any query params that might have been used.
\WP_Rest_Cache_Plugin\Includes\Caching\Caching::FLUSH_LOOSE: Delete caches by an endpoint path matching any cache that was called starting with the endpoint path (ignoring any query params or subpaths following the given path).

2. $force: Should the caches be deleted ($force = true) or just flushed ($force = false).

Hi @rorymheaney

Thank you for your really nice review!
Please let us know if we can be of any assistance, if you are missing functionalities or if you have any suggestions!

The Item API Caches are caches of a single item from a multi-item endpoint. So for instance the /wp-json/wp-/v2/posts contains multiple posts. Now let’s say this endpoint contains the posts with the id’s 1, 2, 3, 4 and 5. Whenever one of these posts is update the endpoint cache for the posts is flushed.
The item caches are caches of the separate posts within that endpoint. This is done so that when for instance the post with id=2 is edited, the posts endpoint is flushed and the item cache for id=2 is also flushed. Now when the posts endpoint is requested again, the posts 1, 3, 4 and 5 are retrieved from the item cache and post 2 is regenerated.

This technique however only works for endpoints that use the WP_REST_Posts_Controller, the WP_REST_Terms_Controller or the WP_REST_Attachments_Controller from the WordPress Core. It doesn’t work for custom endpoints (even not when they extend one of those controllers), because in order for this to work we extend those controllers.