Disabling Cache Status Messages (or minifying HTML) breaks Cache Tester
-
Found a pretty large bug in the plugin. Figured this one out after a couple minutes of playing around.
My cache testing was noting that the “Timestamps differ or were not found,” but the debug log was clean. Everything was loading as expected, and caching was performing beautifully.
After spending quite a bit of time trawling through every possible variable that could have been affecting this, and reading through numerous support threads of people experiencing similar issues, I found the issue.
If you disable “Cache Status Messages” in the debug menu, the cache timestamps cannot be tested.
I’d recommend either noting to the user that Cache Status Messages must be turned on for testing to work, or explicitly bypassing the setting for Cache test pages (the better option IMO).
Finally, any kind of code minification that strips out HTML comments also breaks the cache tester.
I experienced this with Cloudflare’s CDN-side HTML minification, and with the WP plugin Autoptimize. This is no fault of the plugin, and getting past it would require a complete re-think of how to test cache timestamps. I’d recommend displaying a message to the user to disable minifying features when the “Timestamps differ” message is shown.
- The topic ‘Disabling Cache Status Messages (or minifying HTML) breaks Cache Tester’ is closed to new replies.
