Title: update changes client-side cache to No
Last modified: September 1, 2016

---

# update changes client-side cache to No

 *  Resolved [Robert Trevellyan](https://wordpress.org/support/users/trevellyan/)
 * (@trevellyan)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/update-changes-client-side-cache-to-no/)
 * When I update Lite to 160706 or Pro to 160709, the client-side cache setting 
   always changes to “No”.
 * [https://wordpress.org/plugins/comet-cache/](https://wordpress.org/plugins/comet-cache/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/update-changes-client-side-cache-to-no/#post-7569204)
 * [@trevellyan](https://wordpress.org/support/users/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.
 *  [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/update-changes-client-side-cache-to-no/#post-7569208)
 * [@trevellyan](https://wordpress.org/support/users/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](https://github.com/websharks/comet-cache/issues/807)
 * Thanks so much for reporting!
 *  Thread Starter [Robert Trevellyan](https://wordpress.org/support/users/trevellyan/)
 * (@trevellyan)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/update-changes-client-side-cache-to-no/#post-7569228)
 * Yes, upgrading changes the setting from Yes to No. Sorry, should have been clearer,
   thanks for the quick response.
 *  [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/update-changes-client-side-cache-to-no/#post-8192468)
 * The latest version of Comet Cache (v160917, released today) includes changes 
   related to this GitHub issue. Please see the full [changelog](https://wordpress.org/plugins/comet-cache/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](https://github.com/websharks/comet-cache/issues/807).

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘update changes client-side cache to No’ is closed to new replies.

 * ![](https://ps.w.org/comet-cache/assets/icon-256x256.png?rev=1348602)
 * [Comet Cache](https://wordpress.org/plugins/comet-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/comet-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/comet-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/comet-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/comet-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/comet-cache/reviews/)

## Tags

 * [update](https://wordpress.org/support/topic-tag/update/)

 * 4 replies
 * 2 participants
 * Last reply from: [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/update-changes-client-side-cache-to-no/#post-8192468)
 * Status: resolved