Serendipity Forums

Hi,

don´t know if it´s a bug. Since yesterday my Twitter Plugin produce a failure report, sometimes one line, sometimes many lines - see screenshot https://skitch.com/roblen/ffp18/firesho ... tform-html

Don´t know that I change something. Since yesterday my Desktopeditor für S9y have a problem to connect to my blog - maybe this is the same failure?

Use Serendipity 1.5.5 und PHP 5.3.6.

Regards
Robert

Maybe it has to do something with
http://www.golem.de/1106/84250.html
and possible API changes?

Maybe... Thank you for the information.

As Twitter will change authentification with end of June the plugin maybe need some other changes...

Hi!

the way I read it it's an issue with bit.ly, their API call might no longer work. I've patched the twitter plugin to fail on that case without an error message, that's the best I can do right now...don't know what happens when bit.ly redirections won't work. You might need to use a different URL shortening service now, if this is not a temporary measure.

I don't have the spare time to keep up with all this sucking BC-breaking API changes. When do developers ever learn to honor backwards compatibility to not break things for "other people"?!?

Regards,
Garvin

Hi Garvin,
thank you for the answer. I can change the short-url service... As Twitter change with July 2011 the authentification method there could be the next reason the make changes on the plugin?

Hi Robert!

I tend not to clutter my free time with keeping up on Twitter API changes as well. To which july 2011 changes are you referring to? I tried to google it, but didn't find specific changes...

Regards,
Garvin

Mhh. I think it´s only a reauthenticating of an app. Then you can decide if the app could see you private messages or not...

robert wrote:Mhh. I think it´s only a reauthenticating of an app. Then you can decide if the app could see you private messages or not...

Ah, I think I've seen that discussion pass by somewhere. I believe the Twitter App does not support reading/sending direct messages, so I suppose this functionality/API change shouldn't be a problem...

(So help me Murphy)

Regards,
Garvin

The problem was not twitter, but bit.ly. They changed their API. It is not available any longer without login and the default login in the code (a demo key) is out of ratio always. So it never produced short urls.

I worked on this and it's working again. You have to enter your bitly login and API key into the plugins configuration, the link where both of it is found, will be there, too.

I have to test this a little (with my changes fixing the tweetback problem) and will put the fixes back into Spartakus later.

I need some betatesters, though.. Anybody who dares?
Robert would be great, as he is using bit.ly / j.mp (both supported now) with his own account.