Title: Plugin conflict with caching plugins (SG Optimizer)
Last modified: January 17, 2025

---

# Plugin conflict with caching plugins (SG Optimizer)

 *  Resolved [Selah](https://wordpress.org/support/users/tubescreamer/)
 * (@tubescreamer)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-with-caching-plugins-sg-optimizer/)
 * Hi, I am using SG Optimizer on my website in conjunction with your plugin, however,
   when WCBoost Wishlist is activated and I test the cache on my homepage, it says
   the page isn’t cached. When I deactivate the plugin and test to see if the page
   is cached, it says that it is cached.

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

 *  Thread Starter [Selah](https://wordpress.org/support/users/tubescreamer/)
 * (@tubescreamer)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-with-caching-plugins-sg-optimizer/#post-18255230)
 * I’ve started a thread on the SiteGround Speed Optimizer WP Plugin here: [https://wordpress.org/support/topic/conflict-with-wcboost-wishlist-plugin/#post-18255227](https://wordpress.org/support/topic/conflict-with-wcboost-wishlist-plugin/#post-18255227)
 * They’ve indicated that the plugin adds a **set-cookie** header, such as the one
   below:
   `set-cookie: wcboost_wishlist_hash=2f839425b24480457461faeb8cd76b58%3A%
   3Aee11c9c47e9fa343f13bede21b6e7553; path=/`
 * The **set-cookie** header indicates that the server is attempting to add a cookie
   to the user’s browser, which suggests that the content might be personalized 
   or session-specific. Caching such responses could lead to serving personalized
   content to the wrong users, compromising functionality and security. Therefore,
   to ensure accurate and secure delivery of content, their caching systems bypass
   caching pages with “Set-Cookie” headers.
 * You say that the plugin works with caching plugins but there seems to be an issue
   here.. Can someone please help look into this?
 *  [lange20](https://wordpress.org/support/users/lange20/)
 * (@lange20)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-with-caching-plugins-sg-optimizer/#post-18261132)
 * I am having the same issue
 *  Plugin Author [WCBoost](https://wordpress.org/support/users/wcboost/)
 * (@wcboost)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-with-caching-plugins-sg-optimizer/#post-18280120)
 * Hello,
 * Thank you for reaching out and reporting the issue with WCBoost Wishlist and 
   SG Optimizer.
 * The core issue stems from how SG Optimizer handles cookies differently from most
   other caching plugins. When SG Optimizer detects any cookies on a page, it chooses
   not to cache that page at all. This is an unusually strict approach, since cookies
   are actually a fundamental part of how modern websites work – they power many
   things from login sessions to shopping carts.
 * Most caching plugins offer more control over cookie handling. You can specify
   which cookies should prevent caching and which shouldn’t.
 * The reason WCBoost Wishlist uses a cookie is for performance optimization. Storing
   the wishlist data in a cookie allows us to avoid loading the wishlist contents
   on every single page load. This is actually the same approach that WooCommerce
   uses for shopping carts.
 * We are actively investigating ways to make our plugin work better with SG Optimizer.
   However, in the meantime, I would strongly recommend switching to a caching plugin
   that offers more flexible cookie handling. WP Rocket, W3 Total Cache, or LiteSpeed
   Cache would all be excellent alternatives. These plugins generally provide options
   to exclude specific cookies from the caching process, allowing your wishlist 
   to function correctly while still enabling page caching.
 * If your caching plugin has a cookie exclusion setting, please add `wcboost_wishlist_hash`
   to the excluded cookies list – this will ensure your wishlist works properly 
   while still allowing page caching for better performance.
    -  This reply was modified 1 year, 4 months ago by [WCBoost](https://wordpress.org/support/users/wcboost/).
 *  Thread Starter [Selah](https://wordpress.org/support/users/tubescreamer/)
 * (@tubescreamer)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-with-caching-plugins-sg-optimizer/#post-18280149)
 * Thank you for the in-depth response.

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

The topic ‘Plugin conflict with caching plugins (SG Optimizer)’ is closed to new
replies.

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

 * 4 replies
 * 3 participants
 * Last reply from: [Selah](https://wordpress.org/support/users/tubescreamer/)
 * Last activity: [1 year, 4 months ago](https://wordpress.org/support/topic/plugin-conflict-with-caching-plugins-sg-optimizer/#post-18280149)
 * Status: resolved