Twitter API 1.1
Permalink
It has come to my attention that Twitter just "retired" the 1.0 version of their API and it is no longer available. This means that any apps (or Cocnrete addons, including my own Social Feed) needs to be upgraded to work with the Twitter API 1.1. Learn more at the link below:
https://dev.twitter.com/blog/api-v1-is-retired...
I wanted to post this in case anyone is wondering why their Twitter feed doesn't work.
https://dev.twitter.com/blog/api-v1-is-retired...
I wanted to post this in case anyone is wondering why their Twitter feed doesn't work.
This Twitter API thing is a real headache! This update means that all old versions of my Social Feed addon are no longer valid and won't work at all.
In answer to your question - there is no reason you can't just re-name your package (you can do this when you edit your marketplace item). I would be sure to mention the change in the description.
In answer to your question - there is no reason you can't just re-name your package (you can do this when you edit your marketplace item). I would be sure to mention the change in the description.
Thanks for the heads up -- never though to just change the title directly on the page (one of those pre-programmed assumptions kicking in I guess). Anyway, I'll probably give it a week before I change the title, etc as I just directed some of the users to pick up version 2.0 and I don't want to cause any undue confusion. Again, thanks for the heads up!
And for some amusement, some of the Twitter forums are filling up with angry web programmers, so its not just us. Reading through is a somewhat therapeutic if you start getting too frustrated by The Great Twitter API Massacre of 2013...
And for some amusement, some of the Twitter forums are filling up with angry web programmers, so its not just us. Reading through is a somewhat therapeutic if you start getting too frustrated by The Great Twitter API Massacre of 2013...
http://www.concrete5.org/marketplace/addons/dkutwittersearch/...
I just recently updated the marketplace with version 2.0, which replaces the search API with the Timeline API. Unfortunately, the Timeline API is FAR less robust, doing its best to prevent its CSS from being updated/manipulated and requiring a widget id from the twitter account holder to even be allowed to display the twitter content. Still, it works, and its a decent alternative to the search API.
Side question: since its not officially no longer a "Twitter Search" package and more of a "Twitter Timeline" package, should I keep everything under the same project or close the old one and start a new one? And if the latter, how do you pull a depricated package from the marketplace?