Last week, Google turned off the long deprecated Google Feed API.
Among many Blogger features that were affected, were 4 identified gadgets.
I setup a test Newsreel gadget, on my test blog, to see for myself.
If you look in the sidebar of my test blog, you can see gadgets "NR 1" and "NR 2". You will notice that both are blank.
My blog, with gadgets "NR 1" and "NR2" at the top of the sidebar. Both gadgets would be invisible, except for the titles.
Newsreel is pretty simple, to setup. It seems that some content, for Blogger, Google, and / or Microsoft should be available?
I tried again, with Kia, Nissan, and Toyota. Nogo on this one, either.
We have a Rollup Topic, in Blogger Help Forum: Get Help with an Issue, where we are requesting details from blog owners who are affected by this outage. If your blog includes a Newsreel gadget, and your gadget is not working, please provide details.
If you have this problem, the resolution may begin with your details - if you are willing to provide them.
(Update 12/8): This problem has been verified as fixed.
Among many Blogger features that were affected, were 4 identified gadgets.
- Feed
- Newsreel
- Slideshow
- Video Bar
I setup a test Newsreel gadget, on my test blog, to see for myself.
If you look in the sidebar of my test blog, you can see gadgets "NR 1" and "NR 2". You will notice that both are blank.
My blog, with gadgets "NR 1" and "NR2" at the top of the sidebar. Both gadgets would be invisible, except for the titles.
Newsreel is pretty simple, to setup. It seems that some content, for Blogger, Google, and / or Microsoft should be available?
I tried again, with Kia, Nissan, and Toyota. Nogo on this one, either.
We have a Rollup Topic, in Blogger Help Forum: Get Help with an Issue, where we are requesting details from blog owners who are affected by this outage. If your blog includes a Newsreel gadget, and your gadget is not working, please provide details.
If you have this problem, the resolution may begin with your details - if you are willing to provide them.
(Update 12/8): This problem has been verified as fixed.
Comments