Troubleshooting Revosoft Cache: Common Issues and Fixes
Efficient caching improves site speed and user experience, but misconfigured or malfunctioning caching can cause errors, stale content, or poor performance. Below are the most common Revosoft Cache problems and clear, step-by-step fixes to get your site back to optimal behavior.
1. Site shows stale or outdated content
- Cause: Cache not purged after content updates; aggressive TTL settings.
- Quick fixes:
- Clear Revosoft Cache from the plugin/dashboard: go to Cache → Purge All.
- If your CDN is enabled, purge CDN cache as well.
- Reduce TTL for dynamic pages (e.g., set homepage TTL to 5–15 minutes during frequent edits).
- When to escalate: If purging via dashboard doesn’t work, flush server-level caches (Redis/Memcached) and check for object-cache drop-in conflicts.
2. Logged-in users see cached pages (session issues)
- Cause: Public cache served to authenticated sessions or missing cache-bypass rules.
- Fixes:
- Enable “Bypass cache for logged-in users” in Revosoft settings.
- Verify cookies and session headers are listed under cache-exclusion rules.
- Test in an incognito window while logged in to confirm behavior.
- Tip: For specific roles that should see uncached content (e.g., editors), add role-based exceptions.
3. Mixed content or broken assets after enabling cache
- Cause: Cache rewrites or URL rewriting interfering with asset paths; HTTPS misconfiguration.
- Fixes:
- Ensure site URL and home URL are HTTPS in CMS settings.
- Enable “Respect origin protocol” or similar setting so cached references use correct scheme.
- Clear cache and CDN; check browser console for blocked asset URLs and correct them.
- When to escalate: If asset paths are rewritten to incorrect domains, disable URL rewriting features and manually correct base URLs.
4. 500 / 502 / 503 server errors after enabling Revosoft Cache
- Cause: Conflicts with server-level caching, insufficient PHP workers, or misconfigured rewrite rules.
- Checks & fixes:
- Temporarily disable Revosoft Cache to confirm it’s the source.
- Inspect server error logs (nginx/apache/php-fpm) for specific error lines.
- Revert recent cache rule changes; disable advanced optimizations (minify/concatenate) and re-enable one at a time.
- Increase PHP workers or adjust timeout settings if backend requests are timing out.
- Note: If errors persist after disabling the plugin, restore from a recent backup and contact hosting support.
5. Cache not clearing automatically on content update
- Cause: Webhook/purge integration failure or misconfigured event triggers.
- Fixes:
- Verify automatic purge options are enabled for post/page updates in Revosoft settings.
- If using a build/deploy system, add a purge command to deployment hooks.
- Test purge endpoint manually (e.g., visit /?revosoftpurge=1 or use the plugin’s purge API).
- When to escalate: If API purge returns errors, check authentication keys and server firewall rules blocking requests.
6. Minification or combination breaks JS/CSS functionality
- Cause: Aggressive minification/combination that changes load order or removes required code.
- Fixes:
- Disable minify/combine options and re-test to confirm.
- Enable minification only for CSS or only for JS, then reintroduce the other to isolate failures.
- Exclude problem files (e.g., vendor scripts or inline-critical scripts) from minification.
- Tip: Use the browser DevTools Network and Console tabs to identify which files fail and adjust exclusions accordingly.
7. Admin dashboard or WP-CLI commands failing with cache enabled
- Cause: Cache locks, stale object-cache drop-ins, or file-permission problems.
- Fixes:
- Temporarily disable Revosoft Cache and any object-cache drop-in (wp-content/object-cache.php).
- Check file and folder permissions for wp-content, cache, and uploads directories.
- Run WP-CLI cache purge commands to reset caches:
Code
wp cache flush
- When to escalate: If CLI and dashboard both fail, examine PHP error logs and consider restoring the object-cache drop-in from a known-good backup.
8. Excessive disk usage in cache directory
- Cause: Long TTLs, cache fragmentation, or large number of cached variants (mobile, geo, cookies).
- Fixes:
- Lower TTLs for non-critical pages.
- Enable cache pruning or set a maximum cache size in Revosoft settings.
- Disable unnecessary cache variants (e.g., separate caches per cookie) to reduce duplicates.
- Tip: Schedule periodic cache purges during low-traffic windows.
9. CDN and origin inconsistent leading to 404s or 403s
- Cause: CDN caching stale routes, origin blocking purge requests, or origin protection rules.
- Fixes:
- Purge both origin and CDN caches after content changes.
- Confirm CDN origin credentials and allowlist CDN IPs in origin firewall.
- Use cache-control headers to instruct CDN behavior (e.g., Cache-Control: no-cache for dynamic endpoints).
Diagnostic checklist (quick)
- Disable Revosoft Cache — does the problem disappear?
- Clear all caches: Revosoft, object cache, CDN, server caches.
- Check server and PHP error logs for stack traces.
- Reproduce in incognito and with plugins/themes disabled (conflict test).
- Re-enable features one at a time (minify, CDN, variants) to isolate the issue.
Useful commands & snippets
- WP-CLI flush:
Code
wp cache flush
- Manual purge endpoint test:
Code
When to contact support
- Persistent 5xx errors after safe-mode troubleshooting.
- Cache API authentication failures that return ⁄403.
- Data-corrupt cache files or permission issues you cannot resolve. Provide: Revosoft plugin version, PHP/nginx/apache logs, steps to reproduce, and recent config changes.
If you want, I can generate a short checklist tailored to your site (CMS, hosting, CDN) — tell me those details and I’ll produce it.
Leave a Reply