We’re also seeing this behaviour on one of our sites (we have seen it in firefox as well though, so I don’t think it’s a browser thing).
We first noticed it on 3rd Jan – at that point the site was running 2.8.4.
We’ve since upgraded to 2.9.1 and are still having the problem.
It’s hard to pin down because it’s so intermittent, and the ‘feed’ that comes up often isn’t actually a proper feed (we saw a ‘feed’ that wordpress named as the title of an image in one of the blog posts)
It can happen on any link, and browser shows the correct url in the address bar but serves up some rss xml.
Active plugins are:
Akismet
All in One SEO Pack
Daily Top 10 Posts
FD Feedburner Plugin (did have ‘FeedBurner FeedSmith’ at first, same issue)
Google XML Sitemaps
Most Commented Widget
Secure and Accessible PHP Contact Form
Yet Another Related Posts Plugin
Any ideas?
We think we’ve found a way to prevent this problem.
We found that by adding ‘/feed’ onto the end of any post or page, you can trigger the problem manually (you will see the same feed that has been coming up random), but by adding ‘/feed/’ on the end of the URL, the correct feed appeared. This shows there is definetly something strange going on.
With the ‘FD Feedburner Plugin’ you are given the option to provide the URL to two feeds to redirect to feedburner; the main feed and the comments feed.
Our previous settings only included a link to the main feed, so all calls to /feed would be redirected to the feedburner website but we did not include a link to redirect the comments feed so that would use the default functionality.
By including a link to redirect the comments feed in the settings I believe it has bypassed the method which was causing the problem (because it will overwrite the default feed functionality so that calls to /feed or /feed/ will redirect to the feedburner website).
It seems, for whatever reason, there is a bug or issue relating to the comments feeds, but by using a plugin like ‘FD Feedburner Plugin’ to override the default functionality, the problem is bypassed.
As far as we can tell this has solved it, though the problem probably still exists if we were to disable that plugin and revert to the default wordpress functionality for feeds.
