wayneatcrossroadtechnologies

Hey John Lyman 🙂

If you have the Pro version you are eligible for support at: http://www.wptouch.com/support/ Get their support there!

Having said that.. I went to: http://www.wptouch.com/support/knowledgebase/optimizing-caching-plugins-for-mobile-use/#W3totalcache

and found these helpful sounding suggestion for using W3 Total Cache:
W3 Total Cache
If you have “Browser Cache” enabled, please disable ‘Set expires header’ in the Browser cache settings to prevent Desktop/Mobile switch link issues.

Go to the “Page Cache” settings under the Performance tab.
Copy the list of mobile user agents found in our list of “User agent list for configuring cache plugins“.
If you have added support for additional mobile devices in WPtouch Pro’s Compatibility > Custom User Agents field, you must also include those user agents in the “Rejected User Agents” area in W3 Total Cache.
Scroll down to the “Rejected User Agents” field and paste the list of WPtouch default user agents, adding one per line.
Save your changes.
Go to the “Minify” settings under the Performance tab.
Scroll down to the “Rejected User Agents” field and paste the list of WPtouch default user agents, adding one per line.
Save your changes.
Go to the “CDN” settings under the Performance tab.
Scroll down to the “Rejected User Agents” field and paste the list of WPtouch default user agents, adding one per line.
Save your changes.
Finally, go to the W3 Total Cache “Dashboard” and select “Empty All Caches”.

Your site should now be configured correctly to work with WPtouch Pro and W3 Total Cache.
If you are running a version of W3 Total Cache released before version 0.9.2.9, you will need to add the wptouch-pro-view cookie in the “rejected cookies” area in the Page Cache settings.
exclude-wptouch-pro-cookie

Exclude WPtouch Pro Cookie

+-=+-=+-=

Hope this helps 🙂

Ditto on the “Great find joivmaco. Thanks!”

UN-fortunately, I also ticked the check box for the Yahoo sign-in…

Got this error message:

Fatal error: Uncaught exception ‘ErrorException’ with message ‘SSL: certificate subject name ‘FG300B3908602133’ does not match target host name ‘me.yahoo.com” in /web1/user/website/wp-content/plugins/addthis-social-sign-in/includes/openid.php:172 Stack trace:
#0 /web1/user/website/wp-content/plugins/addthis-social-sign-in/includes/openid.php(261): LightOpenID->request_curl(‘https://me.yaho…’, ‘GET’)

#1 /web1/user/website/wp-content/plugins/addthis-social-sign-in/includes/openid.php(395): LightOpenID->request(‘https://me.yaho…’)

#2 /web1/user/website/wp-content/plugins/addthis-social-sign-in/includes/openid.php(559): LightOpenID->discover()

#3 /web1/user/website/wp-content/plugins/addthis-social-sign-in/addthis_social_sign_in.php(406): LightOpenID->authUrl()

#4 /web1/user/website/wp-content/plugins/addthis-social-sign-in/addthis_social_sign_in.php(217): addthis_ssi_yahoo(”)

#5 [internal function]: addthis_social_sign_in(‘addthis_social_…’, Array)

#6 /web1/user/website/wp-includes/ in /web1/user/website/wp-content/plugins/addthis-social-sign-in/includes/openid.php on line 172

=-==-=-=-=–=
line 172 says:
if (curl_errno($curl)) {
throw new ErrorException(curl_error($curl), curl_errno($curl));

and line 42 says that:
* The library requires PHP >= 5.1.2 with curl or http/https stream wrappers enabled..

Some webhosting companies do not enable curl unless you ask them to.
Obviously the case here.

Don’t see anywhere to enable http/https stream wrappers…

So for now I “un” ticked the Yahoo authentication… Shame

OH YEAH – the file

/plugins/addthis-social-sign-in/includes/openid.php

had NO closing ?> at the bottom of the file.

Well, if I get some more time to look at this I’ll update what I’ve learned 🙂