Title: Chrome issues
Last modified: August 22, 2016

---

# Chrome issues

 *  Resolved [jono_39](https://wordpress.org/support/users/jono_39/)
 * (@jono_39)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/)
 * I’m finding that it’s not working on Chrome, but seems to be fine on Safari and
   Firefox.
 * Running multisite 3.9.2 on Wpengine servers with SSL certificate across the network.
 * [https://wordpress.org/plugins/user-switching/](https://wordpress.org/plugins/user-switching/)

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

 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228375)
 * Have you updated from a previous version of User Switching? If so, did it work
   correctly before?
 * What happens when you try to switch? Do you get any errors?
 *  Thread Starter [jono_39](https://wordpress.org/support/users/jono_39/)
 * (@jono_39)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228500)
 * Yes I did update from a previous version and it did work correctly before.
 * I’m hosting my multisite network on wpengine and strangely it works fine on my
   staging server which was pushed from my live site.
 *  I don’t get any errors, just doesn’t work.
 *  Thread Starter [jono_39](https://wordpress.org/support/users/jono_39/)
 * (@jono_39)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228502)
 * The only difference between live and staging is that staging has no cache and
   no SSL, but again, works fine on staging.
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228520)
 * Thanks. I’ve had another user report an issue too. I’ll look into it in the next
   day or so.
 *  Thread Starter [jono_39](https://wordpress.org/support/users/jono_39/)
 * (@jono_39)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228543)
 * So, it seems to work perfectly on Firefox 31.0 for mac
 * Everything but “Switch off” works on Safari 7.0.6
 * Barely anything works on Chrome 37.0.2062.94
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228601)
 * Do you have any other plugins active which may be interfering with the login 
   process or interfering with cookies on your site? Or are you running any funky
   browser extensions? I can see no reason this would break in Chrome and Safari
   but be fine in Firefox.
 *  Thread Starter [jono_39](https://wordpress.org/support/users/jono_39/)
 * (@jono_39)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228606)
 * I have tested it against all the other plugins I’m running and didn’t find any
   that conflicted. I also disabled all the browser extensions I use and it did 
   not solve the issue.
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [11 years, 8 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228611)
 * I’m afraid I’m at a loss as to what to suggest. I can’t even think of anything
   you could try. If it works fine in Firefox then that means the issue can’t be
   server-side, and it can’t be related to your SSL setup. It could be a caching
   issue, but I would still expect you to see the issue in all browsers.
 * My only guess would be that there is some sort of network issue causing User 
   Switching’s cookies to not get sent, but even then I would expect it to affect
   all browsers.
 * If you like, you can send over the credentials for an admin account on the site(
   [email address here](https://johnblackbourn.com/about)) and I’ll take a look 
   when I’ve got some free time.
 *  [jjacobs_amg](https://wordpress.org/support/users/jjacobs_amg/)
 * (@jjacobs_amg)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228696)
 * I’ve noticed the same issue on a WPEngine hosted multisite. It definitely seems
   to be a caching issue, but I believe it’s a browser cache related issue and not
   related to WPEngine’s cache. I say this because I have had it work in Chrome 
   before, but after working for a certain period of time it would stop working.
   The same happened with Firefox. When I first brought up Firefox, it worked just
   fine, then after a while it stopped. I eventually opened up an private window
   in Firefox and it was working just fine.
 * Perhaps the solution would involve blocking browsers from caching data associated
   with User Switching and finding a way to confirm that the plugin’s cookies do
   in fact get sent. Unfortunately that’s not my forte.
 * Aside from that issue, great plugin!

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

The topic ‘Chrome issues’ is closed to new replies.

 * ![](https://ps.w.org/user-switching/assets/icon.svg?rev=3193956)
 * [User Switching](https://wordpress.org/plugins/user-switching/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/user-switching/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/user-switching/)
 * [Active Topics](https://wordpress.org/support/plugin/user-switching/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/user-switching/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/user-switching/reviews/)

## Tags

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

 * 9 replies
 * 3 participants
 * Last reply from: [jjacobs_amg](https://wordpress.org/support/users/jjacobs_amg/)
 * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/chrome-issues-2/#post-5228696)
 * Status: resolved