`\n<\/code><\/pre>\n\ndefine( 'NB_CACHE_PURGER_SECRET_ID', 'your-secret-id' );\ndefine( 'NB_CACHE_PURGER_SECRET_KEY', 'your-secret-key' );\n `<\/p>\n\n
Then in WordPress admin:\n1. Go to \"Settings\" \u2192 \"Naibabiji Cache Purger\"\n2. Fill in the Zone ID<\/strong> (Secret ID and Secret Key will be automatically loaded from constants)\n3. Choose other options and save<\/p>\n\nMethod 2: Direct Configuration in Admin<\/h3>\n\n\n- Log in to WordPress admin<\/li>\n
- Go to \"Settings\" \u2192 \"Naibabiji Cache Purger\"<\/li>\n
- Fill in the following information:\n\n
\n- Secret ID<\/strong>: Tencent Cloud API Secret ID<\/li>\n
- Secret Key<\/strong>: Tencent Cloud API Secret Key<\/li>\n
- Zone ID<\/strong>: EdgeOne Zone ID<\/li>\n<\/ul><\/li>\n
- Choose other options:\n\n
\n- Enable Auto Purge<\/strong>: Whether to automatically purge cache when posts are updated<\/li>\n
- Purge Method<\/strong>:\n\n
\ndelete<\/code>: Directly delete node cache<\/li>\ninvalidate<\/code>: Mark as expired, revalidate from origin<\/li>\n<\/ul><\/li>\n- Enable Logging<\/strong>: Whether to log purge operations<\/li>\n<\/ul><\/li>\n<\/ol>\n\n
Nginx Cache Integration (Optional)<\/h4>\n\n
Only needed if your server uses Nginx FastCGI cache or Proxy cache (configured via fastcgi_cache_path<\/code> or proxy_cache_path<\/code> in nginx.conf). Most sites using WordPress cache plugins do not need this.<\/p>\n\n\n- In \"Settings\" \u2192 \"Naibabiji Cache Purger\" \u2192 scroll to the Nginx Cache Integration<\/strong> section at the bottom<\/li>\n
- Check Enable Nginx Cache Purge<\/strong><\/li>\n
- Enter the absolute filesystem path to your Nginx cache zone directory (e.g.
\/var\/run\/nginx-cache<\/code>)\n\n\n- The web server process (e.g.
www-data<\/code>) must have write permission to this directory<\/li>\n- The settings page will validate the path and show whether it is writable<\/li>\n<\/ul><\/li>\n
- Save settings \u2014 Nginx cache will now be cleared automatically every time EdgeOne cache is purged<\/li>\n<\/ol>\n\n\n
Method 1: Upload<\/h4>\n\n\n- Download the plugin zip file<\/li>\n
- Log in to WordPress admin dashboard<\/li>\n
- Go to \"Plugins\" \u2192 \"Add New\" \u2192 \"Upload Plugin\"<\/li>\n
- Select and upload the plugin zip file<\/li>\n
- Activate the plugin<\/li>\n<\/ol>\n\n
Method 2: Manual Installation<\/h4>\n\n\n- Upload the plugin folder to the
wp-content\/plugins\/<\/code> directory<\/li>\n- Log in to WordPress admin dashboard<\/li>\n
- Go to \"Plugins\" page<\/li>\n
- Find \"Naibabiji Cache Purger for EdgeOne\" plugin and activate it<\/li>\n<\/ol>\n\n\n
\nWhat is EdgeOne?<\/h3><\/dt>\nEdgeOne is Tencent Cloud's edge computing and CDN service that provides global content delivery and security features.<\/p><\/dd>\n
Why do I need to purge cache?<\/h3><\/dt>\nWhen you update content on your WordPress site, EdgeOne may serve cached versions. This plugin ensures visitors see the latest content immediately.<\/p><\/dd>\n
Is this plugin secure?<\/h3><\/dt>\nYes, the plugin supports storing API credentials in wp-config.php, keeping them out of the database and admin interface.<\/p><\/dd>\n
What URLs are purged when a post is updated?<\/h3><\/dt>\nThe plugin automatically purges:\n* The post\/page URL\n* Homepage\n* Category archives the post belongs to\n* Tag archives the post has\n* Author archive\n* Date-based archives= Do I need the Nginx Cache Integration? =<\/p>\n\n
No, it is optional. Only enable it if your server uses Nginx-level page caching (FastCGI cache or Proxy cache). If you use WordPress cache plugins such as WP Rocket, W3 Total Cache, or LiteSpeed Cache, you do not need this feature.<\/p><\/dd>\n
What is the difference between Nginx cache and EdgeOne CDN cache?<\/h3><\/dt>\nEdgeOne CDN cache is distributed across edge nodes worldwide and is managed via the Tencent Cloud API. Nginx cache is a server-side page cache stored on your own server's filesystem, managed by Nginx's fastcgi_cache<\/code> or proxy_cache<\/code> directives. They are separate caching layers; this plugin can clear both at the same time.<\/p><\/dd>\nWhy does the plugin keep the Nginx cache directory itself instead of deleting and recreating it?<\/h3><\/dt>\nDeleting and recreating the directory creates a brief window where Nginx may fail to write new cache entries. By only deleting the contents and keeping the directory, the purge is safer and avoids potential Nginx errors.<\/p><\/dd>\n
The Nginx cache path shows \"not writable\" \u2014 how do I fix it?<\/h3><\/dt>\nThe PHP process (typically www-data<\/code> or nginx<\/code>) needs write permission on the cache directory. Run chown www-data:www-data \/your\/cache\/path<\/code> or chmod 755 \/your\/cache\/path<\/code> as appropriate for your server setup.<\/p><\/dd>\n\n<\/dl>\n\n\n2.2.0<\/h4>\n\n\n- Improved \"Purge All\" behavior: It now only clears the cache for the current site's hostname (using purge_host) instead of the entire zone. This prevents unintentional cache clearing of other subdomains sharing the same EdgeOne Zone ID.<\/li>\n<\/ul>\n\n
2.1.0<\/h4>\n\n\n- Complete rebranding: Renamed plugin to Naibabiji Cache Purger for EdgeOne.<\/li>\n
- Deep refactoring of all internal classes, namespaces, and file structures for better maintenance.<\/li>\n
- Switched all internal database option keys to standardized lowercase
nb_cache_purger_<\/code> prefix.<\/li>\n- Updated all hooks, transients, and nonces to use unified
nb_cache_purger_<\/code> branding.<\/li>\n- Improved security and trademark compliance.<\/li>\n<\/ul>\n\n
2.0<\/h4>\n\n\n- Complete code refactoring with modern PHP namespace architecture<\/li>\n
- Added asynchronous purge mode support (configurable via settings)<\/li>\n
- Added purge statistics dashboard showing total purges, success rate, and breakdown by reason<\/li>\n
- Enhanced log sanitization to protect sensitive API credentials<\/li>\n
- Improved admin bar menu with parent-child structure (EdgeOne \u2192 Purge All \/ Settings)<\/li>\n
- Enhanced security: sensitive input fields hidden when constants are defined in wp-config.php<\/li>\n
- Modular code structure for better maintainability and extensibility<\/li>\n
- Improved error handling and detailed API response logging<\/li>\n
- Updated UI\/UX to match 1.4 interface while maintaining 2.0 functionality<\/li>\n
- Restored Chinese translations for all interface elements<\/li>\n
- Added settings entry on plugin list page<\/li>\n
- Improved manual purge interface with separate sections for Post ID and Custom URLs<\/li>\n
- Enhanced logging with better error messages and request tracking<\/li>\n<\/ul>\n\n
1.4<\/h4>\n\n\n- Added Nginx server-side cache integration (FastCGI cache \/ Proxy cache)<\/li>\n
- Nginx cache path is validated in real time on the settings page (existence, writeability)<\/li>\n
- Nginx cache and EdgeOne CDN cache are cleared independently \u2014 failure of one does not block the other<\/li>\n
- Nginx purge result is recorded in the purge log when logging is enabled<\/li>\n
- New settings are disabled by default and clearly marked as optional to avoid confusion for users who do not use Nginx cache<\/li>\n
- Added Settings shortcut link on the Plugins list page<\/li>\n
- Added EdgeOne node to the admin bar with quick Purge All Cache and Settings links<\/li>\n<\/ul>\n\n
1.3<\/h4>\n\n\n- Improved localization and language files<\/li>\n<\/ul>\n\n
1.2<\/h4>\n\n\n- Added custom URL purge functionality for static resources (CSS, JS, images)<\/li>\n
- Added directory prefix purge support using trailing slash (\/)<\/li>\n
- Fixed cache plugin hook detection logic<\/li>\n
- Improved timing control for plugin initialization<\/li>\n
- Enhanced manual purge with full site purge support<\/li>\n
- Added force mode for cache plugin integrations<\/li>\n
- Improved logging with prefetch result display<\/li>\n
- Added manual log clearing functionality<\/li>\n
- Fixed X-TC-Timestamp header type safety<\/li>\n
- Updated WordPress 6.0+ compatibility<\/li>\n
- Enhanced settings descriptions for clarity<\/li>\n<\/ul>\n\n
1.1<\/h4>\n\n\n- Added cache plugin integration (WP Super Cache, W3 Total Cache, WP Rocket, LiteSpeed Cache)<\/li>\n
- Added optional cache prefetching functionality<\/li>\n
- Improved error handling and logging<\/li>\n<\/ul>\n\n
1.0<\/h4>\n\n\n- Initial release<\/li>\n
- Automatic cache purge on post publish\/update\/delete<\/li>\n
- Manual purge functionality<\/li>\n
- Comment integration<\/li>\n
- Flexible configuration options<\/li>\n
- Logging support<\/li>\n<\/ul>","raw_excerpt":"Automatically purge Tencent Cloud EdgeOne cache when WordPress posts are published, updated, or deleted.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/296113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=296113"}],"author":[{"embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/naibabiji"}],"wp:attachment":[{"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=296113"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=296113"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=296113"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=296113"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=296113"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/fa.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=296113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}