@trevellyan Are you saying that it reverts to “No” after an upgrade, or that you cannot change it to “Yes” because it always reverts to “No” after saving the settings?
I just tested Comet Cache Lite v160706 and confirmed that enabling Client-Side Caching works just fine.
@trevellyan After running a few more tests, I’ve confirmed that this is a bug. It appears to be related specifically to the upgrade routines that run when upgrading from a version prior to v160706 to either v160706 or v160709, as you mentioned.
I’ve filed a bug report here and I’ll make sure this is fixed in the next update: https://github.com/websharks/comet-cache/issues/807
Thanks so much for reporting!
Yes, upgrading changes the setting from Yes to No. Sorry, should have been clearer, thanks for the quick response.
The latest version of Comet Cache (v160917, released today) includes changes related to this GitHub issue. Please see the full changelog:
Bug Fix: Fixed a bug where upgrading from v160521 would result in the Client-Side Cache option being reset to the default (disabled). If you enabled the Client-Side Cache at some point, now is a good time to double-check that it’s still enabled. This bug fix also improves the reliability of all version upgrade routines that Comet Cache runs during upgrades. See Issue #807.
