jump to navigation

Feed Croaked, Sorry!
October 11, 2008

Posted by Dan Edelen in : Blogging, Technical

Functions : Trackback, Print This Post Print This Post , Email This Post Email This Post

Readers,

I spent most of last night repairing the feed for Cerulean Sanctum. I have no idea what happened. The feed simply got corrupted on some level. Took me hours to fix.

Problem was that everything looked fine on my end. Then I noticed that the number of readers through Feedburner was down by 60 percent. That’s not unusual as glitches occur on their end from time to time, but I checked it anyway and found it was on my end, not theirs. And it’s never on my end.

If your feed is not working for this blog, please let me know. For some reason, Bloglines still has not refreshed, but everyone else seems okay. Not sure why the numbers are still hugely down on Feedburner, but everything is working fine from their end, so who knows.

Thanks!

Share/Save/Bookmark

Tags: , , , , ,


Related posts:

RSS feed | Trackback URI

3 Comments »

Comment by Don Subscribed to comments via email
2008-10-13 13:25:41

Looks like Bloglines still hasn’t refreshed.

Comment by Dan Edelen
2008-10-13 14:21:11

Yeah, Don, and I don’t know why. They claim they refresh every hour, but I fixed my feed on Friday night. It checks out right everywhere else. Validates, too.

Comment by Don Subscribed to comments via email
2008-10-13 15:55:56

Dan,

Well, if that is the case, then I guess that I have no choice but to unsubscribe. Of course I will be turning right around and subscribing again. :)

I have some other feeds in Bloglines that were showing the same status as yours. They also seem to be served but by Feedburner.

Thanks for publishing such a great blog.

Don

 
 
 
Name (required)
E-mail (required - never shown publicly)
URI
Subscribe to comments via email
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.

Trackback responses to this post