My client and I are ready to throw rotten fruit in frustration over Feedburner. I can’t tell if this is a Feedburner thing or if it’s something to do with the source feed in EE missing something that Feedburner needs, but I’ve NEVER had this big of an issue and we’re at our wit’s end. Hopefully, someone has some insight? Here’s the skinny:
Hey folks. As the client, I wanted to add a few things, though Joelle speaks EE more fluently than I do!
The Feedburner feed will only update if I force it to resync. Hence it’s up to date at the moment because I just kicked it.
Feedburner is also not talking to iTunes, which adds another layer of WTF. iTunes is like a passive aggressive romance heroine: “You did something wrong and I’m not speaking to you but I’m not telling you what it is that you did.”
I’m hoping that fixing the Feedburner/EE issue (if there is one) with my regular RSS feed for the blog will give me a clue what to try next to fix the iTunes feed, which is also run via Feedburner.
Sorry to hear about the frustration here! In my limited experience with FeedBurner, I can attest to how finicky it can be. It really wants a very well-formed feed. Have you tried validating your feed? It looks like there are some things that could be tweaked there. Similarly, FeedBurner has a “Troubleshootize” menu. Have you looked into any suggestions it might offer? Does FeedBurner offer any kind of feedback about why it’s not updating?
I have indeed tried the “troubleshootize” tab, both to resync the feed when the other suggestions have proven unhelpful. What’s bizarre is that this is the same feed as before my recent redesign, and it worked before. NO idea why it’s not working now, and the responses from Feedburner’s troubleshooting process aren’t very explanatory.
At least it’s better than iTunes, which just doesn’t tell me anything!
And it still doesn’t update unless you manually ping it. Nothing we do seems to force it to update at 30min intervals, which is how often Feedburner checks for updates.
The source feed itself displays beautifully and updates as it should. I’ve Googled quite a bit and can’t seem to find anyone else with this *particular* issue, though have seen people complain in general about Feedburner.
I think I may have found a potential cause in Troubleshootize, though I’m not sure how to determine the size of one’s feed.
The trouble: Your Original Feed is too doggone big! FeedBurner does not process feeds that are larger than 512K. Remember, your feed is an update on your content — not an archive for it — and you should use your publishing tools’ controls to make sure your feed doesn’t grow like kudzu possessed.
Ok, latest info: I just made some adjustments to the source feed per the invalidity reported in the Feedburner feed itself. I tried to manually ping using this link: http://www.feedburner.com/fb/a/ping but it did not update instantly, as described (and as usual).
I know this isn’t a direct answer, but I’m dealing with the same issue with another client, and have been unable to find a resolution. Feedburner hasn’t been updated by Google in more than a year, and I’m actively looking for alternatives.
Yes, all the feeds update as they should. We’ve tried 3 different templates now, both atom and RSS and they all work according to plan. All update. It’s just not picking up in Feedburner, for whatever reason.
Well… I hate to say it, but that might mean that Feedburner’s just not a viable option then. And while I don’t want to trash them on a public forum, the Feedburner brand does seem to be one that Google’s not really keeping up anymore.
Personally I have had mini battles with FeedBurner over years and have since dropped it.
My alternative was just to to provide the standard feed though so I don’t have any alternatives for you in that respect.
Is PingShot still a feature/service of FeedBurner?