Anonymous User 16850768
(@anonymized-16850768)
Cache Enabler creates cached pages based on output buffering. In simple terms, that means we take the HTML that your WordPress website is going to send to the browser and save it as a static HTML file on your server’s disk. It’s possible there is a conflict, like if a third party plugin is unintentionally closing our output buffer. We’ve had cases with other plugins like that in the past. With that said, unfortunately I can’t say for certain why this occurred due to lack of information about the issue and not even given the chance to investigate this further.
If you genuinely didn’t want this to happen to anyone else I believe you would have opened a support thread to allow us to troubleshoot what occurred. Without this, how are improvements supposed to be made? WordPress and its entire ecosystem would not be what it is today without that. I’d recommend considering a different path of resolution the next time that you encounter an issue. It’s not only helpful for developers but the community as well.
Feel free to open a support thread at any time if you’re in need of our direct assistance.
I appreciate your response and you should know that I always provide feedback. I have published plugins of my own, so I know how valuable it is.
But this time, there is no way I could have kept the plugin activated and asked for support.
Among other not so important pages, it caused a vital money page on my site to become deindexed by Google, which resulted in hundreds of $ in losses. How would I possibly keep it activated at that cost?
Actually, I wouldn’t even be able to reproduce the bug, it was random. After clearing the cache, the page was re-cached as it should have been originally. The worst type of bug…
I checked the error log, but it didn’t have anything related to this.
Would it help if I sent you the plugins active on the site?
