SMF 2.1.4 has been released! Take it for a spin! Read more.
Started by enik, January 28, 2011, 06:55:21 PM
Quote from: JoliePittOnline on October 11, 2012, 01:39:14 AMHi 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
Quote from: Colin on October 11, 2012, 02:15:41 AMI 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.
Quote from: JoliePittOnline on October 11, 2012, 02:51:58 AMColin, I just did it and it worked. Thank you very much for your help!
Quote from: Taylor Singletary 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
Quote from: Taylor SingletaryIf 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 ExpandGood: https://api.twitter.com/1/statuses/user_timeline.json?screen_name=episodBad: https://twitter.com/statuses/user_timeline/episod.jsonBad: https://api.twitter.com/statuses/user_timeline/episod.jsonBad: https://twitter.com/1/statuses/user_timeline/episod.jsonBots 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.
Good: https://api.twitter.com/1/statuses/user_timeline.json?screen_name=episodBad: https://twitter.com/statuses/user_timeline/episod.jsonBad: https://api.twitter.com/statuses/user_timeline/episod.jsonBad: https://twitter.com/1/statuses/user_timeline/episod.json
Quote from: enik on October 29, 2012, 09:59:28 PMthe problem is that twitter servers upgraded their apis, so this mod and no longer work in this way, I will look and update itSorry for the inconvinients.Regards enik...