Title: Conflict with caching plugin
Last modified: August 24, 2016

---

# Conflict with caching plugin

 *  Resolved [barkingbird](https://wordpress.org/support/users/barkingbird/)
 * (@barkingbird)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/)
 * I recently switched to ZenCache for a caching solution but lost mobile detect
   functionality. When I disable ZenCache, mobile detect works.
 * Can you recommend a caching solution that doesn’t conflict with Mobile Detect?
 * My htaccess file:
    ********************************************** # Use PHP54
   Single php.ini as default AddHandler application/x-httpd-php54s .php
 * <IfModule mod_deflate.c>
    <IfModule mod_filter.c> AddOutputFilterByType DEFLATE
   text/plain text/html application/x-httpd-php-source AddOutputFilterByType DEFLATE
   text/xml application/xml application/xhtml+xml application/xml-dtd AddOutputFilterByType
   DEFLATE application/rdf+xml application/rss+xml application/atom+xml image/svg
   +xml AddOutputFilterByType DEFLATE text/css text/javascript application/javascript
   application/x-javascript AddOutputFilterByType DEFLATE font/truetype application/
   x-font-ttf font/opentype application/x-font-otf </IfModule> </IfModule>
 * # BEGIN WordPress
    <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule
   ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME}!-
   d RewriteRule . /index.php [L] </IfModule>
 * # END WordPress
 * ***************************************
    I moved the coding between and including
   BEGIN WordPress and END WordPress to the the top just above the IfModule mod_deflate
   code, but without success.
 * [https://wordpress.org/plugins/addfunc-mobile-detect/](https://wordpress.org/plugins/addfunc-mobile-detect/)

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

 *  Plugin Author [Joe Rhoney](https://wordpress.org/support/users/joerhoney/)
 * (@joerhoney)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042803)
 * I don’t think your .htaccess is the problem. Especially if activating/deactivating
   ZenCache affects whether or not it’s working. You can remove your .htaccess code
   from this post, I don’t see anything that is likely to start the header too early(
   which is usually what interferes). Most likely it has to do with the way ZenCache
   works (based on what you said). I don’t have a lot of experience with caching
   yet, but I understand [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
   is good. Have you tried that?
 *  Plugin Author [Joe Rhoney](https://wordpress.org/support/users/joerhoney/)
 * (@joerhoney)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042818)
 * Any luck with this, barkingbird?
 *  Thread Starter [barkingbird](https://wordpress.org/support/users/barkingbird/)
 * (@barkingbird)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042819)
 * I deactivated another plugin called Slimstat, which is a very good and robust
   analytics plugin, but which tends to have some serious conflict issues with other
   plugins. After deactivation, no problems. Thanks! Resolved.
 *  [Jason Crouse](https://wordpress.org/support/users/coolmann/)
 * (@coolmann)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042822)
 * I’d like to know how Slimstat was affecting the site, so that we can investigate
   the issue on our end and patch the code as needed 🙂
 *  Plugin Author [Joe Rhoney](https://wordpress.org/support/users/joerhoney/)
 * (@joerhoney)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042833)
 * Great [@barkingbird](https://wordpress.org/support/users/barkingbird/)! Thanks
   for letting me know. 🙂
 * [@camu](https://wordpress.org/support/users/camu/), the only thing I can say 
   on that is that what I’ve seen interfere with AddFunc Mobile Detect often, is
   when other developers include Mobile_Detect.php in their plugin/theme, but don’t
   wrap their include properly to see if the Mobile_Detect class already exists.
   For instance:
 *     ```
       if( !class_exists( 'Mobile_Detect' ) ) {
          // Include Mobile_Detect.php
       }
       ```
   
 * So it could have something to do with that. Otherwise, it would be best to check
   with the Slimstat developers.
 *  [Jason Crouse](https://wordpress.org/support/users/coolmann/)
 * (@coolmann)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042834)
 * Okay thank you 😉 By the way, I am one of the developers!
 *  Plugin Author [Joe Rhoney](https://wordpress.org/support/users/joerhoney/)
 * (@joerhoney)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042852)
 * Ah! Ha ha! Well, good! Always happy to work with others to make things more compatible
   for people. 🙂

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

The topic ‘Conflict with caching plugin’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/addfunc-mobile-detect_1c0d1e.svg)
 * [AddFunc Mobile Detect](https://wordpress.org/plugins/addfunc-mobile-detect/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/addfunc-mobile-detect/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/addfunc-mobile-detect/)
 * [Active Topics](https://wordpress.org/support/plugin/addfunc-mobile-detect/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/addfunc-mobile-detect/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/addfunc-mobile-detect/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)
 * [mobile detect](https://wordpress.org/support/topic-tag/mobile-detect/)

 * 7 replies
 * 3 participants
 * Last reply from: [Joe Rhoney](https://wordpress.org/support/users/joerhoney/)
 * Last activity: [10 years, 8 months ago](https://wordpress.org/support/topic/conflict-with-caching-plugin/#post-6042852)
 * Status: resolved