Subscribe to rss rss

FeedBurner Migrated To Google

Posted by : | On : 04-03-2009 | Comments (0)
FeedBurner Migrated To Google
Are you a blogger that wants to deliver news to your readers? How can you do that? Can your user subscribe to your blog and get the latest blog post? Yes, if you’re using WordPress, one can subscribe to you using the RSS feeds located on your blog. Now the question though, is how to keep track on the amount of readers on your blog? One possible way is by using FeedBurner. But then something changed!!!! Google acquired Feedburner a few months back, and while I was using Feedburner, the feeds don’t seem to be updated. Using Google Reader to read my feeds, I detect that my feed wasn’t updated and decided to have a check on Feedburner. It looks like Google has migrated the feed reading of Feedburner to another domain name. Now instead of www.feedburner.com, one should access to the new feeds using feedburner.google.com. But of course if you’re an exisiting user of feedburner, log in first to feedburner.com to move your feeds to the new feeds in feedburner.google.com so that you can get your new feed link. If you’re still clueless on what are feeds and stuffs, here’s where one can get started. Start by trying to click on the Subscribe to RSS logo on the top right or on this FEED LINK itself. You’ll learn more. Or Subscribe By Clicking This Giant RSS Icon In that way, after choosing your reader, you can now catch the latest news from your favorite blog.

FeedBurner Gone Error 500

Posted by : | On : 17-10-2008 | Comments (0)
FeedBurner Gone Error 500
Seemingly, it’s another bad year for me. Or rather a bad few days. I had a complaint from one of my online contacts that my Feed wasn’t showing up well, so I went to search over the Internet the causes of it. I thought it was a temporary glitch on Feedburner. Little did I know, it was more than that. After that my readers all didn’t get their feeds for a long time and I got this error screen Bang! Kapowww! Krakk! Error 500!! Now you’ve seen it, how the heck did I rectify this error then? Solution well, I did finally fix this error. I found out the culprit was the translator plugin which I put on and that somehow affected my Feedburner and made it gone haywire. So now whenever you have this error, check for your latest plugin in your wordpress that you’ve inserted. A code there might affect the Feedburner from doing it’s job. I hoped my experience helped you people out there
f54ccc2c13f4dbf05aeee5ec2125deca58bdb9bbeca7fd7b1e