Thread: A warning about W3 Total Cache plugin and Adsense...

A warning about W3 Total Cache plugin and Adsense...

Today while looking at my site, I noticed on the bottom of the page where my Adsense ads should be located was a single line of text reading: "Code corrupted. Insert fresh copy.". At first I thought maybe my Adsense code was hacked somehow so I happily repasted the code but got the same error.

I then went to view the page source and everything was compressed - no linefeeds and minimal spacing. Aha! Then I remembered I implemented W3 Total Cache the other night! This plugin has the ability to "minify" javascript files among other things. I changed the settings under Minify for JavaScript to no longer remove linefeeds and viola! My Adsense came back.

Hopefully that's the only setting I have to change.

Re: A warning about W3 Total Cache plugin and Adsense...

Are there any significant benefits for such a plug in?

Re: A warning about W3 Total Cache plugin and Adsense...

Well, the two biggest advantages from what I understand are:
#1. memcached - which "is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load." It's only useful if your host provider has in installed.

#2. Transparent content delivery network (CDN) support which will offload various objects like photos, javascript, css and more onto a selected CDN. I'm trying out SimpleCDN at http://www.simplecdn.com/

Additionally, this plugin will "minify" css, javascript and more.

More here: http://wordpress.org/extend/plugins/w3-total-cache/

And I'm taking a huge leap and moving away from shared hosting and putting everything onto a virtual private server (VPS) so I can control just about anything, and get better performance overall.

A lot of this is new to me so I'm learning as I go.

Re: A warning about W3 Total Cache plugin and Adsense...

Would you be able to either send me the HTML or allow me to test a private page that has the symptom to which you refer?

@jschodde is right. The plugin basically gives your blog all of the power that major companies like twitter, facebook etc put into their applications. Testing shows no less than 50% performance improvement over wp super cache for example, and that's only testing the page cache. The plugin caches/compresses/minifies feeds, CSS, JS and also caches your database objects. It's typical to find sites that took ~6-8s to load loading in ~3s after the plugin is fully configured.

Re: A warning about W3 Total Cache plugin and Adsense...

W3 Total Cache are great with a VPS solution... but I have a shared hosting

Re: A warning about W3 Total Cache plugin and Adsense...

It is also 100% compatible with shared hosting. Give it a try, you don't even have to change any settings to make WordPress 50% faster.

Re: A warning about W3 Total Cache plugin and Adsense...

I try it for some months in 2 different blog (one old but updated WP with many post and one new with a fresh WP install with the default post). I have a GS plan to MediaTemple.
In ALL cases the WP run more slow with the plugin than no cache plugin. !?

I'm returning to WP Super Cache (seems not more updated) and the WP run more fine...

Re: A warning about W3 Total Cache plugin and Adsense...

I'm sorry to hear that, but you should know that it's not possible. The cause can only be improper installation. You can see some testimonials here, the plugin is quite robust: http://twitter.com/w3edge/favorites" onclick="window.open(this.href);return false;

Re: A warning about W3 Total Cache plugin and Adsense...

I know, is strange. But I think W3TC is for different target (CDN, APC etc.), especially for who have money to spent into a VPS solution + CDN (+ LiteSpeed ). For this reason I think W3TC is great for a dedicated hosting solution.

Re: A warning about W3 Total Cache plugin and Adsense...

I don't understand. W3TC specifically works on any shared host by default. APC etc is not required. CDN can work even on shared hosting. Please read the FAQ etc.