When I republish my blogs to my FTP server, the atom.xml and rss.xml files are empty.or
I published a new post, and feed file size is 0. Tried republishing template/settings and deleting the rss.xml file, but it still publishes with a 0 file size.or
I recently selected "Publish Entire Blog" from the dashboard settings and now both the rss.xml and atom.xml files are zero bytes. I have tried republishing selected entries and the entire blog again but to no avail, the feeds are still blank.
We also had one very insightful and interesting post.
I see the file here:
but it is at 0 in my FTP here:
This observation is very useful. It points out that the problem isn't the feed, it's the involvement of FTP Publishing. I verified the observation - "www.blogger.com/feeds/8073700612434047107/posts/default" isn't empty, though "www.afnews.info/public/afnews/atom.xml" is empty. Other blogs, given the actual blog URL, will help us verify this observation.
If your blog is suffering from this problem, can you please find a thread in Blogger Help Group: Publishing Trouble or Something Is Broken (there are several threads, in each forum, take your pick), and provide details about your problem.
- What's the URL of the blog? (If the blog has multiple URLs, this could be very important).
- What's the URL of the problem feed?
- Is the blog published to BlogSpot, to Google (as a custom domain), or to an external server (using FTP publishing)?
- Is the feed published only to Blogger / BlogSpot (native Blogger feed), or is it redirected (FeedBurner et al)?
- When did you first observe the problem?
- When did you last not observe the problem?
- If the blog uses FTP publishing, can you look inside each folder below the root, for an unexpected "atom.xml" / "rss.xml" file?
- If the blog uses FTP publishing, can you please provide all relevant FTP settings?
The blog that you save may be your own, if you can help us out.
(Update 3/28 06:00): It appears that, possibly as part of some changes to Blogger yesterday, this problem has resurfaced.
(Update 3/14 19:00): We are seeing multiple reports that the problem appears to be resolved.
I was able to republish my index earlier this evening and again just now and both files are non-empty.