Current Version: Feedburner 2.03
Feedburner is a plugin for Shaun Inman’s Mint. It will display Feedburner feed statistics within Mint. Feedburner is powered by the PHP Addicted To Feedburner API Class.
Screenshot

Features
- Displays the past year of Feedburner statistics.
- Supports multiple Feedburner feeds.
- Supports item tracking.
- Optional caching with configurable expire time.
Download Feedburner
Current Version: 2.03
Released: 2009-01-09
Compatible With Mint 2.0+
21 Comments
Can you tell me what exactly the “Hit’s portion of this means?
Hits is the total number of times your feed was accessed during the given time frame. On the day section the total is the actual number and on the weeks and months sections it’s the average.
wooo, i can not wait longer to test this pro-stat enabled peppr. could you please just send it to my email box? thanx
It’s great Ronald, but i don’t get it, should I use my ID ? (simonalibert in my case, I’ve got 3 feeds) or the ID of one my feeds in the URL in my control panel like 1201357 ?
Thanks a lots !
Just use your public id (the part after feeds.feedburner.com/).
I keep getting this:
Error: Feedburner Awareness API is not enabled. Log into Feedburner to enable it.
I don’t see where to enable it in Feedburner.
NM!
It’s under publicize, for anyone else confused.
I’m unable to get the “Feedburner Items” pane to work. The “Feedburner” main pane seems to be working, so it should not be Awareness API related…
Hello Jeroen,
Do you have the Feedburner Pro features enabled? You can enabled it by clicking on your feed name, and in the bottom of the sidebar selecting FeedBurner Stats.
@Ronald
Yeah, it was something Feedburner related.
It’s working now.
I seem to be having some sort of problem with my “Items” setions as well. I’m getting this error:
Error: No item statistics. If you just enabled item tracking, wait a day for statisics to appear.
It was working just fine earlier and I do have statistics. Any idea what might have happened?
Lee, I’m seeing the same thing on my local install. It appears Feedburner is having API trouble again. Unfortunately the only thing we can do is wait it out.
Hi Ronald,
I’ve just installed the plug-in today and added my feedburner ID, but I get the following error message when I view Mint:
Error:
Error: (1) Feed Not Found
Any help you can offer would be much appreciated. Thanks,
Steve
Steve, that’s an error from Feedburner. They’re saying the feed title you provided does not exist on their server. Double check you entered the correct feed title, and if you do have the correct one, make sure you have the API enabled on your account.
Well, Feedburner were bought by Google and the new awareness api is at https://feedburner. google.com/api/awareness instead of the one that the Pepper uses. It may be that your new feed is at the Google address, and not the old Feedburner one.
Thanks Ronald. I’ve made the API ‘active’ (a couple of days ago) but I’m still getting the error message. Any other suggestions? Thanks,
Steve
2.03 will fix the issues with Google’s new API. Should be approved by Shaun shortly and will appear in the Peppermill.
I just installed the pepper, but I’m getting the following error. Any idea what I’m doing wrong?
Error:
Error: () error setting certificate verify locations: CAfile: /usr/local/share/curl/curl-ca-bundle.crt CApath: none
Thanks,
Joe
I´m getting the same error Message
Error Getting Feed Report:
Error: () error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none
Installed the newest Version of Mint and the FeedBurner Pepper too.
Has somebody an idea?
Greetings,
Michael
I’ll be taking a look at this over the next couple of days. The switch to Google appears to have a few random issues associated with it.
At first glance, the issue does not appear to be directly related to Feedburner, but I’ll take a closer look.
For those of you with issues, stay tuned. They have been heard and fixes are in the works. There is a major announcement regarding plugin development (with an easier way to keep track of development news) on the blog. Feel free to read the announcement while you wait for the new version.