Title: Cache Issue
Last modified: January 7, 2025

---

# Cache Issue

 *  Resolved [trevellfr](https://wordpress.org/support/users/trevellfr/)
 * (@trevellfr)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/)
 * Hi!
 * I am trying to use your plugin to find products on my website, and I am having
   some issues with WP Rocket optimization!
 * I read on the forum that I can exclude the plugin’s code:
 * [https://wordpress.org/support/topic/search-not-displaying-correctly/](https://wordpress.org/support/topic/search-not-displaying-correctly/)
 * I am wondering if this fix is still effective?
 * Thanks.

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

 *  [Kris](https://wordpress.org/support/users/c0nst/)
 * (@c0nst)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/#post-18231464)
 * Hi [@trevellfr](https://wordpress.org/support/users/trevellfr/)!
 * Yes, this solution should still work. However, it solves a problem when WP Rocket
   removes FiboSearch inline styles. I don’t know if your problem is exactly that.
   Could you describe it in more detail?
 * Best regards,
   Kris
 *  Thread Starter [trevellfr](https://wordpress.org/support/users/trevellfr/)
 * (@trevellfr)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/#post-18231703)
 * Of course !
 * Here is an image that summarizes all the explanations!
 * With rocket :
 * [https://ibb.co/Gt1r55V](https://ibb.co/Gt1r55V)
 * Without rocket :
 * [https://ibb.co/89msRVK](https://ibb.co/89msRVK)
 * I unable the css optimisation of rocket for the moment but it isn’t the best 
   way ! Before disable it I add the exlusion css we spoke about and that didn’t
   work well.
 * Thk for your awnser,
 * Best regards.
 *  Thread Starter [trevellfr](https://wordpress.org/support/users/trevellfr/)
 * (@trevellfr)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/#post-18232800)
 * Hi !
 * I tried it, but the issue persists. I contacted WP Rocket, and they provided 
   me with this solution, exclude:
 * `.et_pb_menu__search-container(._) (._).et_pb_menu__search
   (._).dgwt-wcas-search-
   wrapp .dgwt-wcas-search-form (.).dgwt-wcas-open(.) (.).dgwt-wcas-open-pirx(.).
   dgwt-wcas-si(._).dgwt-wcas-content-wrapp
 * With that, everything works. But there are a lot of files to exclude! Are all
   these exclusions necessary?
 *  [Kris](https://wordpress.org/support/users/c0nst/)
 * (@c0nst)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/#post-18240352)
 * Hi [@trevellfr](https://wordpress.org/support/users/trevellfr/)!
 * Yes, I believe this is necessary for FiboSearch to function properly. However,
   the amount of CSS involved isn’t substantial. In fact, nearly all of it is actively
   used, and the FiboSearch styles file itself is compact, minified, and weighs 
   just 37 KB.
 * Best regards,
   Kris
 *  Thread Starter [trevellfr](https://wordpress.org/support/users/trevellfr/)
 * (@trevellfr)
 * [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/#post-18247700)
 * Super !
 * Great.

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

The topic ‘Cache Issue’ is closed to new replies.

 * ![](https://ps.w.org/ajax-search-for-woocommerce/assets/icon-256x256.png?rev=
   2883754)
 * [FiboSearch - Ajax Search for WooCommerce](https://wordpress.org/plugins/ajax-search-for-woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ajax-search-for-woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ajax-search-for-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/ajax-search-for-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ajax-search-for-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ajax-search-for-woocommerce/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [trevellfr](https://wordpress.org/support/users/trevellfr/)
 * Last activity: [1 year, 4 months ago](https://wordpress.org/support/topic/cache-issue-65/#post-18247700)
 * Status: resolved