站长帮

<p><strong>核心功能亮点</strong></p>
<p>🚀 智能缓存刷新<br />
– 文章/页面发布或更新时自动刷新相关 CDN 缓存<br />
– 评论提交及审核通过后即时更新展示<br />
– 支持首页、分类页、标签页等核心页面的缓存管理</p>
<p>⚡ 性能优化<br />
– 可选预缓存功能加速内容分发<br />
– 当前支持腾讯云 CDN 和 EdgeOne 的 API<br />
– 轻量化设计，不影响网站运行效率</p>
<p>🛠️ 便捷管理<br />
– 直观的中文管理界面<br />
– 完善的错误日志系统<br />
– 支持多场景刷新策略配置</p>
<p>🔌 扩展友好<br />
– 采用模块化架构设计<br />
– 预留多 CDN 服务商接口<br />
– 持续更新维护</p>
<p><a href="https://www.zhanzhangb.cn/wordpress-cdn-plugins" rel="nofollow ugc"><span aria-hidden="true" class="wp-exclude-emoji">→</span> 插件官方文档</a></p>
<h3>安装指南</h3>
<ol>
<li>通过 WordPress 后台「插件」<span aria-hidden="true" class="wp-exclude-emoji">→</span>「安装插件」上传安装</li>
<li>在插件页面点击「启用」</li>
<li>前往「设置」<span aria-hidden="true" class="wp-exclude-emoji">→</span>「CDN 缓存管理」完成配置</li>
<li>输入腾讯云 API 密钥（SecretId/SecretKey）</li>
<li>根据需求配置缓存刷新策略</li>
</ol>
<h3>常见问题</h3>
<h4>如何获取腾讯云 API 密钥？</h4>
<p>访问腾讯云 <a href="https://console.cloud.tencent.com/cam/capi" rel="nofollow ugc">API 密钥管理控制台</a> 创建密钥对</p>
<h4>为什么缓存刷新失败？</h4>
<ol>
<li>检查 API 密钥是否有效</li>
<li>确认网络连接正常</li>
<li>查看插件错误日志获取详细信息</li>
<li>参考<a href="https://www.zhanzhangb.cn/wordpress-cdn-plugins#FAQ" rel="nofollow ugc">故障排除指南</a></li>
</ol>
<h3>隐私声明</h3>
<p>本插件仅通过官方 API 与 CDN 服务商交互，传输必要信息包括：<br />
– 需要操作的 URL 列表<br />
– 用于身份验证的 API 密钥<br />
– 操作类型标识符</p>
<p>我们不会收集或存储您的网站数据。腾讯云服务隐私政策：<br />
https://cloud.tencent.com/document/product/301/11470</p>
<h3>技术支持</h3>
<p>由 <a href="https://www.zhanzhangb.cn" rel="nofollow ugc">站长帮</a> 专业团队维护<br />
在线支持：<a href="https://wordpress.org/support/plugin/zhanzhangb-tcdn/" rel="ugc">社区问答</a><br />
– 技术文档：https://www.zhanzhangb.cn/<br />
– 精品资源：https://www.zhanzhangb.com/</p>


站长帮 – WordPress CDN 缓存管理插件

专业的 WordPress CDN 缓存自动化管理解决方案，无缝对接腾讯云 CDN 和 EdgeOne 服务。当您发布或更新文章、发表评论或评论通过审核时，系统将自动触发相关页面的 CDN 缓存刷新，确保访客始终获取最新内容。

奶爸建站笔记

<p>A powerful WordPress plugin that automatically purges Tencent Cloud EdgeOne cache when your posts, pages, or custom post types are published, updated, or deleted.</p>
<h3>External services</h3>
<p>This plugin connects to the Tencent Cloud EdgeOne API (https://teo.tencentcloudapi.com) to provide cache purging and prefetching functionality.</p>
<p>It sends the Following information to Tencent Cloud when a purge or prefetch operation is triggered (e.g., when a post is updated, or when manual purge is used):<br />
*   Tencent Cloud API Credentials (SecretId): Used for request authentication and signing.<br />
*   EdgeOne Zone ID: Used to identify the specific site/zone in EdgeOne.<br />
*   Target URLs or Paths: The specific resources that need to be cleared or prefetched from the CDN nodes.</p>
<p>This service is provided by “Tencent Cloud”: <a href="https://cloud.tencent.com/document/product/301/127483" rel="nofollow ugc">Terms of Service</a>, <a href="https://cloud.tencent.com/document/product/301/11470" rel="nofollow ugc">Privacy Policy</a>.</p>
<h3>Features</h3>
<h4>Automatic Cache Purge</h4>
<ul>
<li>Automatically purges cache when posts are published, updated, or deleted</li>
<li>Supports all public post types (posts, pages, and custom post types)</li>
<li>Smart purge: automatically refreshes post pages, homepage, category archives, tag archives, author archives, and date archives</li>
</ul>
<h4>Comment Integration</h4>
<ul>
<li>Automatically purges related post cache when new comments are approved</li>
</ul>
<h4>Manual Purge</h4>
<ul>
<li>Support for manual purge of specific posts or entire site</li>
<li>Quick purge buttons in admin panel for recent posts</li>
</ul>
<h4>Flexible Configuration</h4>
<ul>
<li>Choose purge method: delete cache (delete) or mark as expired (invalidate)</li>
<li>Optional logging of purge operations</li>
<li>Secure key configuration via wp-config.php constants</li>
</ul>
<h4>Cache Plugin Integration</h4>
<ul>
<li>Automatically purges EdgeOne cache when popular WordPress cache plugins clear their cache</li>
<li>Supports WP Super Cache, W3 Total Cache, WP Rocket, and LiteSpeed Cache</li>
<li>Force mode ensures cache plugin integrations work even when auto purge is disabled</li>
<li>Proper timing control ensures compatibility with all cache plugin loading sequences</li>
</ul>
<h4>Cache Prefetching</h4>
<ul>
<li>Optional cache prefetching after purging (disabled by default)</li>
<li>Only prefetches post URLs, not archive pages to conserve EdgeOne prefetch quota</li>
<li>Ensures first visitor gets cached content immediately</li>
<li>Prefetch results are displayed in the purge logs for easy monitoring</li>
</ul>
<h4>Enhanced Logging</h4>
<ul>
<li>Detailed logging of all purge operations with success/failure status</li>
<li>Manual log clearing functionality for easier debugging</li>
<li>Prefetch operation results displayed alongside purge results</li>
<li>Job IDs and error messages for easy troubleshooting</li>
</ul>
<h4>Advanced Manual Purge</h4>
<ul>
<li>Optimized host-specific “Purge All” using the purge_host method</li>
<li>Manual purge operations are not affected by auto purge settings</li>
<li>Force mode support for cache plugin integrations</li>
<li>Comprehensive URL coverage for post-related purges</li>
</ul>
<h4>Custom URL Purge</h4>
<ul>
<li>Purge cache for specific URLs (CSS, JS, images, etc.)</li>
<li>Support for directory prefix purge using trailing slash (/)</li>
<li>Batch processing: enter multiple URLs, one per line</li>
<li>Automatic URL validation and filtering</li>
<li>Smart type detection: files use purge_url, directories use purge_prefix</li>
</ul>
<h4>Nginx Cache Integration</h4>
<ul>
<li>Optionally clear Nginx server-side page cache (FastCGI cache or Proxy cache) alongside EdgeOne CDN cache</li>
<li>Configured separately — most sites using only WordPress cache plugins do not need this</li>
<li>Nginx cache and EdgeOne cache are cleared independently; either can succeed even if the other fails</li>
<li>Includes path validation with real-time feedback in the settings page</li>
<li>Uses ngx_cache_purge module for precise URL-based cache clearing (faster and more efficient)</li>
<li>Added “Purge Endpoint Path” option for customizable Nginx purge URL path (e.g., use a random string like /xK9mPurge_q7z for better security)</li>
<li>Uses HTTPS requests to your site’s own domain for purge, avoiding HTTP-to-HTTPS redirect issues</li>
<li>Friendly error messages in purge logs: clearly explains why a URL wasn’t cached (e.g., “Not cached — the page was returned instead of a purge response”) instead of showing raw HTML</li>
<li>Fallback to file deletion for full-site purge operations</li>
<li>Detailed per-URL purge logging for Nginx cache operations</li>
</ul>
<h4>No SDK Required</h4>
<ul>
<li>Direct API calls, no need to install Tencent Cloud SDK</li>
<li>Compatible with all WordPress versions 5.5+</li>
</ul>
<h3>Configuration</h3>
<h4>Get Tencent Cloud API Keys</h4>
<ol>
<li>Visit <a href="https://console.cloud.tencent.com/cam/capi" rel="nofollow ugc">Tencent Cloud Console</a></li>
<li>Create or get your <code>SecretId</code> and <code>SecretKey</code></li>
</ol>
<h4>Get EdgeOne Zone ID</h4>
<ol>
<li>Visit <a href="https://console.cloud.tencent.com/teo" rel="nofollow ugc">EdgeOne Console</a></li>
<li>Select your site and find the Zone ID (format: zone-xxxxxx)</li>
</ol>
<h4>Configure Plugin</h4>
<p>There are two configuration methods:</p>
<h3>Method 1: Using wp-config.php (Recommended)</h3>
<p>Add these constants to your WordPress <code>wp-config.php</code> file:</p>
<pre><code>define( 'NB_CACHE_PURGER_SECRET_ID', 'your-secret-id' );
define( 'NB_CACHE_PURGER_SECRET_KEY', 'your-secret-key' );
</code></pre>
<p>Then in WordPress admin:<br />
1. Go to “Settings” <span aria-hidden="true" class="wp-exclude-emoji">→</span> “Naibabiji Cache Purger”<br />
2. Fill in the <strong>Zone ID</strong> (Secret ID and Secret Key will be automatically loaded from constants)<br />
3. Choose other options and save</p>
<h3>Method 2: Direct Configuration in Admin</h3>
<ol>
<li>Log in to WordPress admin</li>
<li>Go to “Settings” <span aria-hidden="true" class="wp-exclude-emoji">→</span> “Naibabiji Cache Purger”</li>
<li>Fill in the following information:
<ul>
<li><strong>Secret ID</strong>: Tencent Cloud API Secret ID</li>
<li><strong>Secret Key</strong>: Tencent Cloud API Secret Key</li>
<li><strong>Zone ID</strong>: EdgeOne Zone ID</li>
</ul>
</li>
<li>Choose other options:
<ul>
<li><strong>Enable Auto Purge</strong>: Whether to automatically purge cache when posts are updated</li>
<li><strong>Purge Method</strong>:
<ul>
<li><code>delete</code>: Directly delete node cache</li>
<li><code>invalidate</code>: Mark as expired, revalidate from origin</li>
</ul>
</li>
<li><strong>Enable Logging</strong>: Whether to log purge operations</li>
</ul>
</li>
</ol>
<h4>Nginx Cache Integration (Optional)</h4>
<p>Only needed if your server uses Nginx FastCGI cache or Proxy cache (configured via <code>fastcgi_cache_path</code> or <code>proxy_cache_path</code> in nginx.conf). Most sites using WordPress cache plugins do not need this.</p>
<ol>
<li>In “Settings” <span aria-hidden="true" class="wp-exclude-emoji">→</span> “Naibabiji Cache Purger” <span aria-hidden="true" class="wp-exclude-emoji">→</span> scroll to the <strong>Nginx Cache Integration</strong> section at the bottom</li>
<li>Check <strong>Enable Nginx Cache Purge</strong></li>
<li>Set a <strong>Purge Endpoint Path</strong> — we recommend using a random string (e.g., <code>/xK9mPurge_q7z</code>) for security, so you can use <code>allow all;</code> in Nginx without exposing the endpoint to attackers</li>
<li>Enter the absolute filesystem path to your Nginx cache zone directory (e.g. <code>/var/run/nginx-cache</code>) — this is only used as fallback when purging the entire site
<ul>
<li>The web server process (e.g. <code>www-data</code>) must have write permission to this directory</li>
<li>The settings page will validate the path and show whether it is writable</li>
</ul>
</li>
<li>Save settings — Nginx cache will now be cleared automatically every time EdgeOne cache is purged</li>
</ol>
<h4>Nginx Purge Configuration</h4>
<p>To use the ngx_cache_purge module integration, you need to configure your Nginx server block with the appropriate purge rules. Replace <code>/xK9mPurge_q7z</code> with your custom purge path:</p>
<pre><code>nginx
location ~ /xK9mPurge_q7z(/.*) {
    allow all;
    deny none;
    fastcgi_cache_purge YOUR_CACHE_ZONE "https$request_method$host$1";
    # Or for proxy cache:
    # proxy_cache_purge YOUR_CACHE_ZONE "https$request_method$host$1";
}
</code></pre>
<p>Replace <code>YOUR_CACHE_ZONE</code> with the name of your Nginx cache zone (e.g., <code>wordpress</code>).</p>
<p><strong>Important notes:</strong><br />
* The <code>fastcgi_cache_purge</code> key (<code>"https$request_method$host$1"</code>) must match your <code>fastcgi_cache_key</code> directive exactly, including the <code>https</code> prefix<br />
* If you are using BT Panel (宝塔) with an HTTP-to-HTTPS redirect rule, the plugin sends HTTPS requests to your own domain, so no additional exclusion rules are needed<br />
* For detailed configuration instructions, see the <a href="https://www.quhenet.com/bt-panel-nginx-fastcgi/" rel="nofollow ugc">configuration tutorial</a></p>


Naibabiji Cache Purger for EdgeOne

Automatically purge Tencent Cloud EdgeOne cache when WordPress posts are published, updated, or deleted.

站长帮 – WordPress CDN 缓存管理插件 vs Naibabiji Cache Purger for EdgeOne