| 开发者 |
acato
rockfire yoeridekker |
|---|---|
| 更新时间 | 2026年10月30日 16:49 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
GET-endpoints.No, the plugin will automatically flush all cache related to the page/post you just edited.
Yes, the plugin will automatically cache the endpoint of custom post types. Unless you have created a custom WP_REST_Controller for it, then it will not automatically cache the endpoint.
Yes, the plugin will automatically cache the endpoint of custom taxonomies. Unless you have created a custom WP_REST_Controller for it, then it will not automatically cache the endpoint.
No, the plugin will not cache your custom endpoint unless you tell it to cache it using our WP REST Cache Pro plugin or the hook wp_rest_cache/allowed_endpoints (See 'Can I register my own endpoint for caching?'). Please keep in mind that once you do so the plugin will not automatically flush the cache of that endpoint if something is edited (it has no way of knowing when to flush the cache). It will however try to determine the relations and for the determined relations it will flush the cache automatically once the relation is edited.
Yes you can! You can use our WP REST Cache Pro plugin to easily register your own endpoints for caching through the wp-admin interface. Or you can do it programmatically by using the hook wp_rest_cache/allowed_endpoints like this:
`/**
Yes you can! Use the hook wp_rest_cache/allowed_endpoints like this:
`/**
Yes you can! Add the GET-parameter skip_cache=1 to your call and no caching will be used.
Yes you can! Use the hook wp_rest_cache/determine_object_type like this:
function wprc_determine_object_type( $object_type, $cache_key, $data, $uri ) { if ( $object_type !== 'unknown' || strpos( $uri, $your_namespace . '/' . $your_rest_base ) === false ) { return $object_type; } // Do your magic here $object_type = 'website'; // Do your magic here return $object_type; } add_filter( 'wp_rest_cache/determine_object_type', 'wprc_determine_object_type', 10, 4 );
Yes they can! Go to Settings > WP REST Cache, on the Settings tab you can check Enable cache regeneration, this will activate a cron job which will check if there are any expired (or flushed) caches and regenerate them. Using the Regeneration interval you can determine how often this regeneration process should run. The Max number regenerate caches limits the number of regenerated caches per regeneration process, this is so your server doesn't get flooded with the regeneration calls.
Yes. Once a day a cron job removes caches from the database that expired more than a day ago, or that were flushed and already cleaned up. This only happens when cache regeneration is disabled, because the regeneration needs these caches to know what to regenerate. Use the filter wp_rest_cache/purge_stale_caches to override this, wp_rest_cache/stale_cache_grace_period to change how long (in seconds) an expired cache is kept and wp_rest_cache/max_purge_caches to change the number of caches removed per run (default 1000).
Yes you can! Use the hook wp_rest_cache/display_clear_cache_button like this:
function wprc_display_clear_cache_button( $show ) { return false; } add_filter('wp_rest_cache/display_clear_cache_button', 'wprc_display_clear_cache_button', 10, 1);
Yes you can! There are two options for this:
Global cacheable request headers. This is a comma seperated list. These headers will be used for ALL endpoints.wp_rest_cache/cacheable_request_headers to specify per endpoint which request headers should be used. Like this:
function wprc_add_cacheable_request_headers( $cacheable_headers ) { $cacheable_headers['wp/v2/posts'] = 'LANG'; return $cacheable_headers; } add_filter('wp_rest_cache/cacheable_request_headers', 'wprc_add_cacheable_request_headers', 10, 1);Yes you can! Use the hook wp_rest_cache/settings_capability like this:
function wprc_change_settings_capability( $capability ) { // Change the capability to users who can edit posts. return 'edit_posts'; } add_filter('wp_rest_cache/settings_capability', 'wprc_change_settings_capability', 10, 1);
Yes you can! Use the wp wp-rest-cache flush command to flush caches. Type wp wp-rest-cache flush --help to see all options.
We are using the WordPress transient API, so as long as you are using a Redis Object Cache plugin which enables Redis caching through the transients API it is supported.
You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team helps validate, triage and handle any security vulnerabilities. Report a security vulnerability.
wp_rest_cache/purge_stale_caches, wp_rest_cache/stale_cache_grace_period and wp_rest_cache/max_purge_caches.
2026.4.1
Release Date: October 29th, 2026
Fix: Deleted caches that had been flushed and cleaned up before were never removed from the database, causing the caches table to grow indefinitely. Existing leftover caches are removed by the cleanup cron. It was reported by krstarica.
2026.4.0
Release Date: October 27th, 2026
Security: Responses generated for authenticated users (e.g. through Application Passwords or Basic auth) could be cached and served to unauthenticated visitors. Requests with an Authorization header and requests with context=edit are no longer cached, responses for authenticated users are only cached if the cache key is user specific, and nonce cached requests are now cached per session. All existing caches are flushed on update.
Feature: Added filter wp_rest_cache/cache_authenticated_response to allow caching of responses generated for authenticated users when the cache key is made user specific.
2026.3.1
Release Date: July 25th, 2026
Improvement: Make the mu-plugin use the same version as the main plugin.
2026.3.0
Release Date: July 24th, 2026
Fix: several small fixes and improvements.
Improvement: Add support for using regex inside wp_rest_cache/allowed_endpoints and wp_rest_cache/disallowed_endpoints filters.
2026.2.0
Release Date: May 19th, 2026
Fix: specified key was too long error.
Improvement: Extra filters and actions.
2026.1.3
Release Date: March 3rd, 2026
Fix: Prevent performance issue with hierarchical categories.
2026.1.2
Release Date: February 25th, 2026
Fix: Prevent PHP warnings.
Improvement: Add filter to disallow skip_cache parameter.
Improvement: Added error log if set_transient fails.
Improvement: Add support for flushing term cache when objects terms are modified. (Contribution by: Moshe Gross)
2026.1.1
Release Date: January 20th, 2026
Fix: A XSS vulnerability in the plugin was discovered and fixed. It was reported by Nguyen Ba Khanh.
Fix: Improved transition_post_status_logic. (Contribution by: Moshe Gross)
2026.1.0
Release Date: January 14th, 2026
Improvement: Only flush caches on meta update if filter returns true.
2025.2.0
Release Date: December 15th, 2025
Improvement: Also flush caches when only the (post) meta is updated.
Earlier versions
For the changelog of earlier versions, please refer to the changelog on Github.