Twitter Changes

11-07-2013

So despite saying that I ain't been ranting lately (wedding entries aside) I ain't been ranting lately. This has somewhat resulted in me not actually being on The Bauble a whole lot. Meaning that when some of the site features fell by the wayside I had no idea they had.

Such as the Twitter Widget. Turns out that Twitter has recently changed their API calls to version 1.1 (or some such shite). End result they no longer supported the widget I was using, it just plain old wasn't showing up any more.

A little copy and paste from Twitter and boom, new widget in place. Sure I think it looks exactly the same as the old one that they got rid of, but hey it's their site they can do what they want.

What I did notice had busted was posts to Twitter. It seems that of the two wedding rants I threw up recently never got pushed to Twitter like rant entries have in the past.

Again this boiled down to the change in API calls. You'd think given the company I work in, one that deals in Social Networks and making API requests to the various sites, I would have paid attention when we had to update our own software because Twitter had changed their code.

Nope, not a bit of it. Straight over my head it went.

Short story long I spent the last hour re-coding The Bauble to get the Twitter stuff working again. I may be somewhat rusty on my PHP but I got it going, so that ain't bad.

Now to leave it weeks before I rant again :D

Blue_jester


Tags: code


Shane | Thu, 11 Jul 13 23:22:13 +0100

In summary: Twitter broke their API in a desperate attempt to help us but even that only saved us from two of Derek's posts.

Leave a comment...

Name (required)