Support for WPColt focuses on clear diagnosis. The most helpful request includes the actual behavior, what you expected to happen, and what changed recently. Cache problems often appear after plugin updates, host migrations, CDN rule changes, WooCommerce changes, or security plugin changes.
Before asking for support
- Clear the cache at each layer you know about: plugin, host, CDN, and object cache where applicable.
- Test in a private browser window while logged out of WordPress.
- Check whether the issue affects all pages or only specific paths such as cart, account, checkout, search, or admin-related URLs.
- Write down any headers you can see, especially Age, X-Cache, CF-Cache-Status, X-Varnish, Cache-Control, and Set-Cookie.
What to include
Include the site URL, the affected URL, your host, active cache plugin, CDN provider, and a short description of the issue. If the problem is stale content, include the time you made the update and the time you still saw the old page.
Common support patterns
The most common issues are duplicate page-cache plugins, cookies preventing cache, server cache running in front of plugin cache, Cloudflare rules caching HTML too aggressively, and object cache drop-ins that exist but are not connected to a Redis or Memcached service.
Paid support
Some issues require a full stack review. When that is the case, WPColt may recommend a paid troubleshooting engagement rather than guessing from partial screenshots.