Title: Compatibility with Autooptimize
Last modified: October 4, 2018

---

# Compatibility with Autooptimize

 *  [chienchou](https://wordpress.org/support/users/chienchou/)
 * (@chienchou)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/)
 * Hi,
 * I think the plugin has compatibility issue with autoptimize. If you access the
   site with ?wmc-currency=BTC. It will return 404 for js files from autoptimize.
   I think it is because this plugin clears autoptimize cache every time when the
   url has wmc-currency for one of the get paramenters.
 * Let me know if you need anything from me. Thanks!
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcompatibility-with-autooptimize%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/compatibility-with-autooptimize/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/compatibility-with-autooptimize/page/2/?output_format=md)

 *  [kimvt1991](https://wordpress.org/support/users/kimvt1991/)
 * (@kimvt1991)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10748279)
 * Hi,
    I see that it works correctly on your site. What is your problem?
 *  [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10748965)
 * > this plugin clears autoptimize cache every time when the url has wmc-currency
   > for one of the get paramenters.
 * is that correct kimvt? because that sounds like a really bad idea to be honest:-/
 * frank (ao dev)
 *  [kimvt1991](https://wordpress.org/support/users/kimvt1991/)
 * (@kimvt1991)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10748989)
 * Yes that’s the only way we know to make it work correctly with autoptimize cache
   now. This happens only when customers switch currency. Do you have any better
   idea?
 *  [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10749130)
 * well, can you explain why you have to do so? what breaks when you don’t do that?
 *  [kimvt1991](https://wordpress.org/support/users/kimvt1991/)
 * (@kimvt1991)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10749377)
 * Cache plugins cause our plugin to show wrong currency symbol. We will do more
   tests to see if it causes any problem.
    [@chienchou](https://wordpress.org/support/users/chienchou/)
   Please open file cache.php(woo-multi-currency/frontend/cache.php) and clear the
   code that we use to clear autoptimize cache(line 52 to 54) and test. If it works
   correctly, we will remove that code from our plugin.
 *  [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10749404)
 * > Cache plugins cause our plugin to show wrong currency symbol
 * Autoptimize is not a (page) cache plugin, it just optimizes the CSS & the JS (
   and optionally images, google fonts, …).
 * > We will do more tests to see if it causes any problem.
 * Great, feel free to reach out (futtta-at-gmail-dot-com) if you need assistance
   🙂
 *  Thread Starter [chienchou](https://wordpress.org/support/users/chienchou/)
 * (@chienchou)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10750741)
 * Hi,
 * I try comment out the code and clear cloudflare and W3 total cache and the js
   error still exists. It looks like it keeps loading a autoptimize file that doesn’t
   exist when the get parameter is present.
 * Do you guys have any idea? Any help is appreciated!
 * [https://www.thechrono.ca/wp-content/cache/autoptimize/js/autoptimize_0a192e2f8f5b2fa2b07c04d5d0f476ad.js](https://www.thechrono.ca/wp-content/cache/autoptimize/js/autoptimize_0a192e2f8f5b2fa2b07c04d5d0f476ad.js)
 *  [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10750796)
 * could be litespeed or cloudflare cache?
 *  Thread Starter [chienchou](https://wordpress.org/support/users/chienchou/)
 * (@chienchou)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10750894)
 * I don’t have litespeed installed and I purged cloudflare cache before checking
   the page again.
 *  [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10750899)
 * you might need to check with your hoster, as you HTTP response headers do mention
   litespeed;
 * ![](https://i0.wp.com/i.imgur.com/vQcjNyw.jpg?ssl=1)
 *  [kimvt1991](https://wordpress.org/support/users/kimvt1991/)
 * (@kimvt1991)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10751731)
 * [@chienchou](https://wordpress.org/support/users/chienchou/) after commenting
   out the code you have to clear autoptimize cache as well.
 *  Thread Starter [chienchou](https://wordpress.org/support/users/chienchou/)
 * (@chienchou)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10754552)
 * I cleared both cloudflare cache and autopmize cache after commenting out add_action(‘
   init’, array( $this, ‘clear_browser_cache’ ) ); in cache.php and the problem 
   still persists. I’ll ask the host to see how to clear litespeed cache.
 *  Thread Starter [chienchou](https://wordpress.org/support/users/chienchou/)
 * (@chienchou)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10782774)
 * Hi [@kimvt1991](https://wordpress.org/support/users/kimvt1991/),
 * Open cache.php(woo-multi-currency/frontend/cache.php) and clear the code that
   we use to clear autoptimize cache(line 52 to 54) solves the issue. Please include
   this in the new version of the plugin.
 *  [kimvt1991](https://wordpress.org/support/users/kimvt1991/)
 * (@kimvt1991)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10783769)
 * Do you get any other issues after that?
 *  Thread Starter [chienchou](https://wordpress.org/support/users/chienchou/)
 * (@chienchou)
 * [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/#post-10786061)
 * [@kimvt1991](https://wordpress.org/support/users/kimvt1991/),
 * Nope. No more 404 errors on autoptimize js file

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/compatibility-with-autooptimize/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/compatibility-with-autooptimize/page/2/?output_format=md)

The topic ‘Compatibility with Autooptimize’ is closed to new replies.

 * ![](https://ps.w.org/woo-multi-currency/assets/icon-128x128.gif?rev=3089832)
 * [CURCY - Multi Currency for WooCommerce - Smoothly on WooCommerce 9.x](https://wordpress.org/plugins/woo-multi-currency/)
 * [Support Threads](https://wordpress.org/support/plugin/woo-multi-currency/)
 * [Active Topics](https://wordpress.org/support/plugin/woo-multi-currency/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woo-multi-currency/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woo-multi-currency/reviews/)

 * 16 replies
 * 3 participants
 * Last reply from: [kimvt1991](https://wordpress.org/support/users/kimvt1991/)
 * Last activity: [7 years, 7 months ago](https://wordpress.org/support/topic/compatibility-with-autooptimize/page/2/#post-10787521)
 * Status: not resolved