Anonymous User 16850768
(@anonymized-16850768)
What version did you update from? What type of installation do you have (e.g. single or multisite)? Can you please provide a direct URL to your website that is encountering this issue along with a screenshot of your current Cache Enabler settings?
Anonymous User 16850768
(@anonymized-16850768)
Just so you and anyone else reading this are aware, if you happen to manually change versions (meaning copying files on your server directly and not using the plugins page) the advanced-cache.php drop-in file in the wp-content directory has to be updated as this can be changed between versions. The matching file that this would need to be updated with resides in wp-content/plugins/cache-enabler. This can be done manually by copying that file over, or allow the plugin to do it by deactivating and then activating the plugin again.
Version Updated from 1.55
Single site.
Very custom setup. WordPress hosted on one domain, served as 100% cached html on another via reverse proxy.
I can’t provide a link to the site where its set up, its no longer set up.
Will look at deleting the advanced-cache.php file to try and get 1.55 going again.
Anonymous User 16850768
(@anonymized-16850768)
To confirm, did you deactivate, uninstall, and then reinstall Cache Enabler when performing the steps above?
If yes, to troubleshoot this further, can you first please provide a screenshot of your Permalink Settings?
I tried all of these things.
a. delete all files, including advanced-cache.php. Install 1.55. Nope.
b. Delete all files again. Reinstall 1.6 from the repository. Nope.
Custom Structure /%category%/%postname%
Wondering if perhaps, its an nginx issue? ALl working fine for many of my other sites, all of which are on apache
Anonymous User 16850768
(@anonymized-16850768)
Thanks for your effort in helping troubleshoot this, @richinberlin99. The permalink structure isn’t an issue, thanks for confirming that.
To clarify, this same issue occurs even on version 1.5.5, meaning it did not start on version 1.6.0 for you? If this same issue does occur on version 1.5.5, does it still occur on version 1.4.9?
1.4.9 works.
If I upgrade to 6, stops working
Anonymous User 16850768
(@anonymized-16850768)
I need clarification on version 1.5.5. Did this start occurring when going from version 1.4.9 to 1.5.5? (Please provide the exact version numbers for clarity.) That would mean this is not related to version 1.6.0 and I need to troubleshoot this elsewhere.
Anonymous User 16850768
(@anonymized-16850768)
Also, if you’re able to provide a list or screenshot of the plugins installed and activated that would be helpful. 🙂 It’s possible the changes made, like the timing on the output buffering, has created a conflict. Are you able to find any potential plugins when comparing your activated plugins on this website to your other sites that are not experiencing this issue?
Anonymous User 16850768
(@anonymized-16850768)
Following up on this issue to see if it’s been resolved yet. Based on your comment in a different thread, did this issue turn out to be related to the Cache Enabler plugin being disallowed by your hosting provider?
Not disallowed per se.
Just not functioning.
Anonymous User 16850768
(@anonymized-16850768)
I’d recommend reaching out to them as they likely have additional information. My best guess at the moment with the information I have is that they may prevent the advanced-cache.php file from being included.
If you’re able to test version 1.4.9 and it works then that would likely be the case. Before version 1.5.0 Cache Enabler could cache and deliver pages through the advanced-cache.php file or later through the plugin itself after it had been initialized (this was indicated through the now removed X-Cache-Handler: php response header).
With the introduction of the cache engine the late delivery was removed as it gave no benefits for Cache Enabler and was quite slow in comparison. It also removed the last duplicate code.
