Title: [Plugin: W3 Total Cache] RSS? Last modified: August 20, 2016 --- # [Plugin: W3 Total Cache] RSS? * [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/) * HI there. I frequently have problems with my RSS feed being out of date. Could this be related to w3 caching the feed? Is it supposed to cache the feed? * Thanks! * [http://wordpress.org/extend/plugins/w3-total-cache/](http://wordpress.org/extend/plugins/w3-total-cache/) Viewing 14 replies - 1 through 14 (of 14 total) * Thread Starter [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526171) * Okay, verified. This thing is definitely caching my RSS feed and it’s not getting updated unless I manually clear the cache. What would cause this? * [Andreas](https://wordpress.org/support/users/sauerland/) * (@sauerland) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526194) * Under Page Cache you might want to try these settings: * Never cache the following pages: wp-.* .php index.php like.php *.xml *.rss * Thread Starter [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526204) * Ahh… cool. Let me try that. * Should I also put: * [http://www.my-site.com/feed/](http://www.my-site.com/feed/) ? * Or is that a fake URL? * Are you sure it’s a good idea to have “index.php” in there? Wouldn’t I want that to cache? * Thread Starter [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526209) * HOLY $*(#@($@#* * Messing with that just 500 error’d my entire site. I’m dead in the water. Can’t even log in. WTF with this plugin? * I’ll report back … * Thread Starter [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526210) * Wow… that was a horrible 30 minutes. * Thank god I know how to FTP in and mess with the htaccess file. Apparently simply adding these two lines to the “do not cache” list: * *.xml *.rss * Completely killed everything. Total 500 error loss. The only way forward was to delete htaccess and rebuild. If I were a novice at this stuff I could have been down for days. W3 cache guys seriously need to know about this. Will email them now… * [Andreas](https://wordpress.org/support/users/sauerland/) * (@sauerland) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526216) * Oops, sorry to hear that. These settings were the default when I installed w3ctc and they’ve done nicely for the last year and still. * But error 500s seem to be another feature of this plugin. I get them quite frequently. * Thread Starter [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526230) * Ha! that’s definitely not good… I’ve let them know. A novice user could be seriously up the creek if that happens. * [RS2OOO](https://wordpress.org/support/users/rs2ooo/) * (@rs2ooo) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526237) * I was following this thread and exactly the same thing happened to my site when I added: * *.xml *.rss * 500 Internal server error, and as a novice I was seriously up the creek. Fortunately my hosting provider is one of the best in the business for service and they fixed my .htaccess for me. * So, unless you know what you are doing, be careful adding those settings to “ never cache the following pages” * There already is a setting in the current version of W3TC for caching/not caching feeds, so I’m wondering if adding this to the “never cache” causes a conflict. * [Daniel J. Lewis](https://wordpress.org/support/users/djosephdesign/) * (@djosephdesign) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526308) * I came to these forums to finally report this problem, too. Are we all running WordPress 3.3? This RSS caching issue showed up after I upgraded. * I’m running WordPress Network. Anyone else? * I’ve had to force refresh my cache whenever I publish a new post. It’s terrible. And I’ve had the same settings that I had in WP 3.2. * W3TC just may not be compatible with WP 3.3 yet. * Thread Starter [nickaster](https://wordpress.org/support/users/nickaster/) * (@nickaster) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526320) * Yeah…. I have latest wordpress. The caching problem seems to have gone away. No idea how. Your still batty? * [Daniel J. Lewis](https://wordpress.org/support/users/djosephdesign/) * (@djosephdesign) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526348) * I can’t quite tell. I forgot to check when I published a new post, but it did show up in the RSS feed overnight. But I also think I remember refreshing my cache anyway after moving a widget (which doesn’t always refresh that cache on its own). * It could be that W3TC is being very slow at updating the RSS cache. * [Daniel J. Lewis](https://wordpress.org/support/users/djosephdesign/) * (@djosephdesign) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526360) * Well, I can tell. I posted two podcast episodes yesterday, each to a separate site on my WordPress 3.3.1 Network. On one site, I had to refresh the cache to remove the widget. That site’s episode was available in the RSS feed. * But on the other site, where I actually posted first around 10:30 last night, the feed still wasn’t updated nearly twelve hours later! * This is unacceptable, and it’s a waste of the cache to have to refresh it every time I post something new. So I’m going to switch to WP Super Cache. * [Andreas](https://wordpress.org/support/users/sauerland/) * (@sauerland) * [14 years, 2 months ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526361) * Well, I haven’t noticed any RSS problems with my sites so far. But there is one thing that should be eyed with suspicion: Total Cache always writes to the main htaccess in the root directory. That is OK as long as you a running a single side or a multisite with clones of the main site. But this might cause a problem or two when you are trying to entertain a blog garden with many different flowers, plugins, scripts, whatnots and individual settings. * I find it rather sad, though, that there hasn’t been an update for half a year or so, because the idea of Total Cache is really neat. * Plugin Contributor [Frederick Townes](https://wordpress.org/support/users/fredericktownes/) * (@fredericktownes) * [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526399) * Part of the issue is with garbage collection. Working on increasing reliability here. Viewing 14 replies - 1 through 14 (of 14 total) The topic ‘[Plugin: W3 Total Cache] RSS?’ is closed to new replies. * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806) * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/) * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/) * 14 replies * 5 participants * Last reply from: [Frederick Townes](https://wordpress.org/support/users/fredericktownes/) * Last activity: [14 years, 1 month ago](https://wordpress.org/support/topic/plugin-w3-total-cache-rss/#post-2526399) * Status: not resolved