{"id":369,"date":"2009-02-09T17:04:05","date_gmt":"2009-02-09T22:04:05","guid":{"rendered":"http:\/\/cssnewbie.com\/?p=369"},"modified":"2009-02-09T17:04:05","modified_gmt":"2009-02-09T22:04:05","slug":"how-to-fix-wordpress-feedburner-plugins-after-converting-to-google-feedburner","status":"publish","type":"post","link":"https:\/\/cssdeck.com\/blog\/how-to-fix-wordpress-feedburner-plugins-after-converting-to-google-feedburner\/","title":{"rendered":"How to Fix WordPress Feedburner Plugins After Converting to Google Feedburner"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/cssdeck.com\/blog\/wp-content\/uploads\/2009\/02\/feedburner-api.gif\" alt=\"Feedburner API\" title=\"Feedburner API\" width=\"579\" height=\"150\" class=\"alignnone size-full wp-image-370\" \/><\/p>\n<p>I ran into (yet another) Feed Count + Feedburner problem recently, shortly after writing my last article on <a href=\"http:\/\/cssnewbie.com\/fixing-a-bad-feedburner-subscriber-count\/\">accounting for Feedburner\u2019s subscriber count mistakes.<\/a> And since I heard from a few people who are also using the Feed Count plugin, I thought I should share this info.<\/p>\n<h3>The Backstory<\/h3>\n<p>As I\u2019m sure all you Feedburner users out there are well aware, Google purchased Feedburner quite some time ago. But until recently, that didn\u2019t mean much: the same people were working on the code, your information was stored in the same place and was represented the same way, and so on.<\/p>\n<p>But recently Google has begun bringing Feedburner more fully into the fold. As a result, all Feedburner users are being required to convert their Feedburner accounts into Google accounts. That created quite a few headaches for lots of people (including myself) right off the bat, as it took a good week for Google to nail down my subscriber numbers with any accuracy \u2013 one day I would have thousands of subscribers, the next I might have zero, and the day following only a few hundred.<!--more--><\/p>\n<h3>A New Problem<\/h3>\n<p>However, even once Google started reporting my Feedburner numbers correctly, I still had a problem: <strong>my Feed Count plugin no longer grabbed my subscription statistics.<\/strong> Now, this wasn\u2019t as huge a problem as it could have been, because I had <a href=\"http:\/\/cssnewbie.com\/fixing-a-bad-feedburner-subscriber-count\/\">my jQuery Feeburner fix<\/a> in place&#8230; but I still wanted my real subscriber stats back at some point.<\/p>\n<p>After a bit of digging, I found the problem: as part of their conversion from Feedburner to \u201cGoogle\u201d Feedburner, <strong>Google changed <a href=\"http:\/\/code.google.com\/apis\/feedburner\/awareness_api.html\">the location of their API.<\/a><\/strong> Thus, any plugins that used the old Feedburner API ceased functioning once that user\u2019s account was successfully ported to Google.<\/p>\n<h3>The Solution<\/h3>\n<p>Long-term, the best solution would be for the plugin developers to update and release new versions of their plugins. But as of now, the Feed Count plugin has not been updated \u2013 and since it hasn\u2019t seen an update since last July, I\u2019m not going to hold my breath on a new version. So I decided to take matters into my own hands and edit my copy of the Feed Count plugin.<\/p>\n<p><strong>Note:<\/strong> this solution is specific to the Feed Count plugin, but any brave souls out there could probably modify and use this information to update other plugins as well.<\/p>\n<p>I opened up my copy of the Feed Count plugin file (feedcount.php) and found this function:<\/p>\n<pre lang=\"php\" escaped=\"true\" line=\"1\">function mapelli_fc_get_defaults() {\n\treturn array(\n\t\t\t'map_fc_feedurl' =&gt; '',\n\t\t  'map_fc_queryurl' =&gt;'http:\/\/api.feedburner.com\/awareness\/1.0\/GetFeedData?uri=',\n\t\t\t'map_fc_lastcount' =&gt; 'N\/A',\n\t\t\t'map_fc_lastupdate' =&gt; 0,\n\t\t\t'map_fc_updateinterval' =&gt; 60, \/\/ 1 h\n\t    'map_fc_error_updateinterval' =&gt; 5, \/\/ 5 min\n\t\t  );\n}<\/pre>\n<p>This function mostly sets all the plugin defaults, but it also sets the \u201cqueryurl\u201d \u2013 the website that the plugin hits to find your subscriber count information. This URL is not customizable anywhere inside WordPress, and since this URL has now changed, we\u2019re forced to edit the plugin itself. <\/p>\n<p>All I had to do was change the \u201cmap_fc_queryurl\u201d line to read this instead:<\/p>\n<pre lang=\"php\" escaped=\"true\" line=\"1\">'map_fc_queryurl' =&gt;'https:\/\/feedburner.google.com\/api\/awareness\/1.0\/GetFeedData?uri=',<\/pre>\n<p>Then I saved the plugin, uploaded it to my server, and my stats started showing up again! However, it\u2019d still recommend putting something like <a href=\"http:\/\/cssnewbie.com\/fixing-a-bad-feedburner-subscriber-count\/\">this JavaScript fix<\/a> in place for those random times when Feedburner drops the ball (and your subscriber count).<\/p>\n<p><strong>Note:<\/strong> Your stats probably won\u2019t start showing up again instantly. You\u2019ll have to wait for the duration of your \u201cupdate interval,\u201d which can be configured in WordPress under Settings -&gt; Feed Count:<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/cssdeck.com\/blog\/wp-content\/uploads\/2009\/02\/feedcount-update-interval.gif\" alt=\"feedcount update interval\" title=\"feedcount update interval\" width=\"579\" height=\"61\" class=\"alignnone size-full wp-image-371\" \/><\/p>\n<p>If you\u2019re using a different plugin and have run into this same problem, please give this solution a try and let people know in the comments if it worked. Thanks! <\/p>\n<div class=\"wp-socializer wpsr-share-icons \" data-lg-action=\"show\" data-sm-action=\"show\" data-sm-width=\"768\" ><h3>Share and Enjoy !<\/h3><div class=\"wpsr-si-inner\"><div class=\"wpsr-counter wpsrc-sz-32px\" style=\"color:#000\"><span class=\"scount\"><span data-wpsrs=\"\" data-wpsrs-svcs=\"facebook,twitter,linkedin,pinterest,print,pdf\">0<\/span><\/span><small class=\"stext\">Shares<\/small><\/div><div class=\"socializer sr-popup sr-32px sr-circle sr-opacity sr-pad sr-count-1 sr-count-1\"><span class=\"sr-facebook\"><a rel=\"nofollow\" href=\"https:\/\/www.facebook.com\/share.php?u=\" target=\"_blank\"  title=\"Share this on Facebook\"  style=\"color: #ffffff\" ><i class=\"fab fa-facebook-f\"><\/i><span class=\"ctext\"><span data-wpsrs=\"\" data-wpsrs-svcs=\"facebook\">0<\/span><\/span><\/a><\/span>\n<span class=\"sr-twitter\"><a rel=\"nofollow\" href=\"https:\/\/twitter.com\/intent\/tweet?text=%20-%20%20\" target=\"_blank\"  title=\"Tweet this !\"  style=\"color: #ffffff\" ><i class=\"fab fa-twitter\"><\/i><\/a><\/span>\n<span class=\"sr-linkedin\"><a rel=\"nofollow\" href=\"https:\/\/www.linkedin.com\/sharing\/share-offsite\/?url=\" target=\"_blank\"  title=\"Add this to LinkedIn\"  style=\"color: #ffffff\" ><i class=\"fab fa-linkedin-in\"><\/i><\/a><\/span>\n<span class=\"sr-pinterest\"><a rel=\"nofollow\" href=\"https:\/\/www.pinterest.com\/pin\/create\/button\/?url=&amp;media=&amp;description=\" target=\"_blank\"  title=\"Submit this to Pinterest\"  style=\"color: #ffffff\" data-pin-custom=\"true\"><i class=\"fab fa-pinterest\"><\/i><span class=\"ctext\"><span data-wpsrs=\"\" data-wpsrs-svcs=\"pinterest\">0<\/span><\/span><\/a><\/span>\n<span class=\"sr-print\"><a rel=\"nofollow\" href=\"https:\/\/www.printfriendly.com\/print?url=\" target=\"_blank\"  title=\"Print this article \"  style=\"color: #ffffff\" ><i class=\"fa fa-print\"><\/i><\/a><\/span>\n<span class=\"sr-pdf\"><a rel=\"nofollow\" href=\"https:\/\/www.printfriendly.com\/print?url=\" target=\"_blank\"  title=\"Convert to PDF\"  style=\"color: #ffffff\" ><i class=\"fa fa-file-pdf\"><\/i><\/a><\/span><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Google has been converting all Feedburner user accounts into Google accounts, which has been creating quite a few headaches. I thought I was done with them, until I noticed my counts still weren&#8217;t showing up on my website. Google had changed the API, requiring a fix on my end. [&#8230;]<\/p>\n<p><a class=\"more-link article\" href=\"https:\/\/cssdeck.com\/blog\/how-to-fix-wordpress-feedburner-plugins-after-converting-to-google-feedburner\/\" title=\"Click to read 'How to Fix WordPress Feedburner Plugins After Converting to Google Feedburner'\">Read Article<\/a><\/p>\n","protected":false},"author":18,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[170,192],"tags":[212,262,266,68,319],"_links":{"self":[{"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/posts\/369"}],"collection":[{"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/comments?post=369"}],"version-history":[{"count":0,"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/posts\/369\/revisions"}],"wp:attachment":[{"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/media?parent=369"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/categories?post=369"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cssdeck.com\/blog\/wp-json\/wp\/v2\/tags?post=369"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}