Calling your twitter 3.0

[Colin]

I see. I would suggest going through and manually removing the modification. You will need to use the modification parser found on the mod page (http://custom.simplemachines.org/mods/index.php?mod=2895). On the right hand side choose your version and select parse. You will need to remove those pieces of code instead of add them, as you are uninstalling the mod, not installing it.

[Colin]

Hi Colin! Actually no. The first time it was okay. Then it wasn't showing my tweets. So I uninstalled it, deleted it on my server. Then the error came up. I tried to install it again to see if it will work, it did work then there were two feeds showing on the Info Center.

http://joliepittonline.org/thegrotto

I just viewed the link you posted and it looks like there is a fatal error. Did you make some other change to SMF as this isn't the error you initial requested assistance with?

[JoliePittOnline]

I see. I would suggest going through and manually removing the modification. You will need to use the modification parser found on the mod page (http://custom.simplemachines.org/mods/index.php?mod=2895). On the right hand side choose your version and select parse. You will need to remove those pieces of code instead of add them, as you are uninstalling the mod, not installing it.

Thank you, Colin. I'll try it now. I apologized for some confusion with the error earlier. It's something I did which does not involved the Twitter mod.

[Colin]

Sounds good, no worries. Keep us updated.

[JoliePittOnline]

Colin, I just did it and it worked. Thank you very much for your help!

[Colin]

Colin, I just did it and it worked. Thank you very much for your help!

So happy to hear that. My pleasure. Let us know if anything else comes up.

[geoff691]

http://miscarriageofjustice.co/index.php

The calling your twitter function has been working well since I installed it months ago but today it is not retrieving any tweets.

I have deleted the files and reloaded them still without success.

Any ideas as to what may be wrong?

Thank you.

[TheListener]

Geoff this may be related to twitter more than smf.

AFAIK all the mod does is display the feed from your twitter onto the forum.

[geoff691]

Thanks mate, maybe there is a temporary fault today.  I will check later.

[geoff691]

It still isn't working today so it looks like back to the drawing board.

Anyone got a suggestion?

[CreativeITWorld.com]

Like everyone elses is saying, great mod. Worked perfect ... until today. The problem definitely is with Twitter though.

Found this when I downloaded the .JSON file connected to our accounts and opened it:

The Link

Code Select Expand

http://twitter.com/statuses/user_timeline/YOURTWITTERACCOUNTNAMEHERE.json?callback=twitterCallback2&count=10

twittercallback2({"errors":[{"message":"Sorry, that page does not exist","code":34}]});


A little further research shows:

https://dev.twitter.com/discussions/11595

Hi Jerry,

I'd verify that you're using the right paths for everything -- we retired unversioned and unsubdomained endpoints yesterday -- so if you're using twitter.com/oauth/* you should use api.twitter.com/oauth/* and if you're using API urls like twitter.com/statuses/user_timeline you should use URLs like api.twitter.com/1/statuses/user_timeline instead. See Following up on API housekeeping for more info.  https://dev.twitter.com/discussions/10803

Judging by the rest of the comments, everybody there has the same problems we are having. I would have thought that we would need to alter the .JSON link to

Code Select Expand

http://api.twitter.com/statuses/user_timeline/YOURTWITTERACCOUNTNAMEHERE.json?callback=twitterCallback2&count=10

But that is apparently incorrect.

From https://dev.twitter.com/discussions/10803

If you're using any kind of "unversioned" endpoint, you'll need to move to a versioned one. Version 1 of the API is still active until March 2013. It's "version zero" of the API that is finally being removed now.

Code Select Expand

Good: https://api.twitter.com/1/statuses/user_timeline.json?screen_name=episod

Bad: https://twitter.com/statuses/user_timeline/episod.json
Bad: https://api.twitter.com/statuses/user_timeline/episod.json
Bad: https://twitter.com/1/statuses/user_timeline/episod.json

Bots are perfectly capable of performing OAuth. A consumer key, secret, access token, and access token secret and a compatible library are all that's necessary.

Assuming the final "Good" line of code works, the remaining problem is the OAuth, which I will gladly leave to the developer.

Good luck.

[Thac0]

Same problem with 2.5 all of the sudden...worked fine one day...and hasn't for the past few days.

Is there a fix that works for this? Any insight will be greatly appreciated. What I've read above, I'm not sure what to do with.

Thanks,

[geoff691]

I'm the same as Thac0 so any help by the developer would be greatly appreciated.

Maybe a new application is needed?

[siammongkol]

Thank you

[Thac0]

.... any input on how to fix this? Update perhaps?  My users really miss this feature on our site as well as I miss how easy it is to get info out to people.

Thx.

[Thac0]

Hmm... no responses. Is this still supported? I'm at a total loss on how to fix this. Should it just be uninstalled for now until some body addresses it? If so, it should also be removed from the MOD section to prevent others from experiencing this issue too.

I hope this is fixed the 80 folks on my site love this feature.

T.

[Thac0]

Can somebody help with this? Please?

[enik]

the problem is that twitter servers upgraded their apis, so this mod and no longer work in this way, I will look and update it

Sorry for the inconvinients.

Regards enik...

[Thac0]

Thank you very much!

[Thac0]

the problem is that twitter servers upgraded their apis, so this mod and no longer work in this way, I will look and update it

Sorry for the inconvinients.

Regards enik...

Just curious... any luck?