matthewbyers77

FYI, i just inquired and got a response back from WP Engine. They said:

“Thanks for getting in touch with us. This is actually a bug we recently documented, and as a result our development team is currently working on identifying a server-wide solution for this issue. That being said, I’ve gone ahead and applied a temporary fix to get this working on our side of things. If you run the test once more, the mobile-friendly tester should see the mobile version of your site.”

This information might be good enough for us to let things ride for awhile. Thanks a lot for Your help!

FYI, i just inquired and got a response back from WP Engine. They said:

“Thanks for getting in touch with us. This is actually a bug we recently documented, and as a result our development team is currently working on identifying a server-wide solution for this issue. That being said, I’ve gone ahead and applied a temporary fix to get this working on our side of things. If you run the test once more, the mobile-friendly tester should see the mobile version of your site.”

This information might be good enough for us to let things ride for awhile. Thanks a lot for Your help!

I see. So WP Engine said that WP Touch would not yet pass the test. What about AMTS? Did You ask them about that or is it the same technology as WP Touch? I’m not familiar with WP Touch.

haha, ugh! I was actually about to put in a support ticket to WP Engine. Good to know about WP Touch. So are You going to expand ATMS to include desktop resolution as well or are You going to recode the whole site to scale without a plugin at all? Thanks for communicating

Thanks for the info. We are also using WP Engine and are aware of their restrictions on caching plugins. I will check out the WP Touch plugin. Redoing our entire site to be fully responsive would be quite an undertaking!

YES! Please help us!

@webcitymedia – so You cleared Your site cache, ran the test, and it worked?! I lost You on the caching part. You think Google is caching the desktop version?

One idea I emailed the ATMS developer about (and haven’t heard a response) was the possibility of detecting for the Googlebot user agent in the plugin itself. The plugin is set up to detect other user agents. Why not just add that one to the list? I’m no wordpress expert, but if I don’t get help soon I may just try to do that on my own. I just can’t believe there aren’t masses of clients out there that are having this exact same issue.