API v1 is retired, old timeline widgets are no-longer rendered

carpling_es · 2013-06-21T15:13:28.000Z

Please help!! followers are unfollowing since this change… could you pleaes provide an alternative for line of code belllow that does the same thing? I have looked and looked and cannot find it …

iantresman · 2013-06-22T17:09:56.000Z

Removing something that works is crazy. If API 1.1 is better, people will migrate. I also notice no help in migrating, ie. if you are using widget.js, then do the following. I also find it odd that the new widget does not let you specify a width, or other colours, which is a very odd claim that API 1.1 is improved.

This is not an encouraging way to treat supporters, so I’ll be recommending that my customers move to tumblr.

iantresman · 2013-06-22T17:19:05.000Z

https://dev.twitter.com/docs/embedded-timelines#customization
I guess this is the replacement, not the Widget page.

lsces · 2013-06-23T14:04:43.000Z

USING the new ‘API’ starts by having to be given access to the clients twitter account - not very good security wise!. But even once one has that access one can’t create a custom display that ACTUALLY matches the site that has now lost a working feed. Like others here I’m working with customers simply to close down their use of Twitter and go to something else - there are a lot of options these days!

stephentruex · 2013-06-24T02:25:09.000Z

You can find the basic pattern on the Embedded Timelines page here https://dev.twitter.com/docs/embedded-timelines

Tweets by @twitterapi

TheSkulleryVan · 2013-06-24T10:47:30.000Z

I am trying to help my friend get Twitter working on her website after your changes.
I have created a new widget and inserted this code into her index page
http://www.rainbowtriketours.co.uk/
Tweets by @RainbowTrikes

Can anyone see why it is not displaying her tweets please?

paniaguai · 2013-06-24T15:28:50.000Z

Twitter plz bring JavaScript back. thks.

benward · 2013-06-24T18:06:20.000Z

You appear to have pasted the embed code inside of another script tag in your page head. Place the code from http://twitter.com/settings/widgets in the page where you want the widget to appear.

HendraDaro · 2013-06-29T18:08:46.000Z

A few days ago, I got a complaint from my customers about this twitter widget bug. It looks like the twitter itself did not have an alternative solution to this problem. And I try persuaded my customers to switch to a fanpage facebook widget. Luckily they were happy with it.

paniaguai · 2013-07-08T20:47:44.000Z

Twitter @benward please may I have my simple embedded Tweet code back ?

Cloud9carhire · 2013-07-09T10:25:40.000Z

that doesnt work for me either using joomla.

Cloud9carhire · 2013-07-09T10:43:54.000Z

I’ve removed twitter feeds from all my sites (50+) and will request clients move to Tumblr. Should be able to do that before Twitter fix this mess.

Well done Twitter! A+ for stupidity.

avoli · 2013-07-13T16:49:45.000Z

Ben it is obvious by your intermittent responses that your watching the discussions around Twitters poor decision to deprecate an API in this manor but you and other Twitter associates fail to have the testicular fortitude to answer these questions.

Very unprofessional and honestly arrogant. We are encouraging alternatives to Twitter.

fundschedule · 2013-07-16T05:09:00.000Z

Possible solution:
Include this after your new widget code. I commented this with the elements I took from the old API to make conversion more easy.

Original from: http://stackoverflow.com/questions/13361823/iframe-css-override-for-new-twitter-widget

fundschedule · 2013-07-16T05:29:46.000Z

Check out my work around to make the “new widget” match the “join the conversation” widget: http://stackoverflow.com/questions/13361823/iframe-css-override-for-new-twitter-widget/17668635#17668635

Image of change: http://img837.imageshack.us/img837/1139/btjc.png

fundschedule · 2013-07-16T05:31:15.000Z

Check out my work around to make the “new widget” match the “join the conversation” widget: http://stackoverflow.com/questions/13361823/iframe-css-override-for-new-twitter-widget/17668635#17668635

Image of change: http://img837.imageshack.us/img837/1139/btjc.png

fundschedule · 2013-07-16T05:32:31.000Z

Check out my work around to make the “new widget” match the “join the conversation” widget: http://stackoverflow.com/questions/13361823/iframe-css-override-for-new-twitter-widget/17668635#17668635

Image of change: http://img837.imageshack.us/img837/1139/btjc.png

Richard_Birks · 2013-07-21T15:16:57.000Z

This is the Henry Ford of widgets. You can have any size and shape of widget as long as it’s black.

If you think for one second that I’m recoding several of the sites that I do for friends to squeeze your highly-limited widget in, you’re very much mistaken. You think I’m going to recommend the Twitter widget to any new sites I code? Dream on…

Welcome to the world of unintended consequences. I’m sure whatever the motivation for changing the back-end code seemed like a good idea at the time, but all you’ve achieved is to substantially reduce the exposure of Twitter on third party sites.

Yep, it takes a strong company to stick by their decisions. You know what though, takes an even stronger company to hold their hands up when that decision was wrong. Your silence on this matter is deafening.

paniaguai · 2013-07-21T17:52:58.000Z

Hello @benward, finally with the new code my embedded widget does n´t look so bad after all.

Check here it here on the top of the page http://gridlink.es/

But, could we remove the word “Tweets” from the header ? it actually obvious it´s tweets.

Thank you.
Best.

benward · 2013-07-22T05:52:30.000Z

Yes, you can hide the header with data-chrome=“noheader” on the embed code.

Ben