You are not logged in.
Anyone any idea why our dev twitter feed seems to be stuck on r3424 on Oct 15th? All this social stuff is beyond me.
Most likely you are using an older plugin that does not authenticate properly with Twitter after the recent change in the authentication process. The latest arc_twitter is ok, I seem to recall that mem_twitter needs updating.
We aren’t using a plugin but I don’t know if the js has been updated at all. Just checking around I can’t see anything obvious. We may have to go down the plugin route cuz of this logging in farce.
They did remove all old APIs (basic auth) couple weeks ago (August 19). Shouldn’t be connected with your problems tho, right?
Last edited by Gocom (2010-11-01 15:07:11)
Rah-plugins | What? I’m a little confused… again :-)
And it looks like we don’t have “curl” so that’s buggered the plugin route. :(
Ah, the old “deprecate and remove the API” trick. That might explain it, though the dates don’t stack up. Hmmm.
Can I leave it with you please, Stuart to figure out the most hassle-free method going forward? If there is such a thing… :-|
(I concur that not having curl (or gzip) installed on the .com/.org sites is somewhat annoying… especially when installing big plugins. Must be a reason for that, but I dunno what it is)
Last edited by Bloke (2010-11-01 15:09:25)
Well whatever the reason for it, it means we can’t use the plugin on either site which would be the simplest route to go down and I’m not seeing anything useful from Twitter at the moment. I shall keep hunting.
Last edited by thebombsite (2010-11-01 15:32:51)
Well actually, now I’ve looked into it a bit more, it would seem that r3424 was the last tweet so the displays on textpattern.com and textgarden are as up-to-date as they can be. I’m not sure how we do tweets. They come in from more than one place, like textpattern, textgarden, svn and I think resources (may be others). I thought Robert controlled that bit. Maybe something else needs updating?
Isn’t TXP.com on Joyent? If so, you can setup curl without any problem by going to the Webmin and editing the php.ini file directly.