graulund / tweetnest

NO LONGER MAINTAINED. MESSAGE ME IF YOU WANT TO MAINTAIN THIS. :) A browsable, searchable and easily customizable archive and backup for your tweets
MIT License
492 stars 93 forks source link

Twitter API 1.1 #50

Closed victorjacobs closed 11 years ago

victorjacobs commented 11 years ago

Hacked in OAuth to comply with Twitter API 1.1.

mkurte commented 11 years ago

Hey there! Looks very nice. Is there a possibility to download your source via github? Last commit of tweetnest is over a year ago, I don't know if this merge will be happen...

victorjacobs commented 11 years ago

Yeah, sure, you can download it right here: https://github.com/victorjacobs/tweetnest/archive/twitter11.zip

ali0une commented 11 years ago

Wow! Amazing work @victorjacobs ... i was about to hack tweetnest to work with new twitter api and you did it! Works 100%. Many thanks, this commit should be merged with @graulund code. Congrats! : )

Centzilius commented 11 years ago

Works perfectly... Thanks

earth2marsh commented 11 years ago

@victorjacobs for some reason I'm getting an error when I hit loadtweets.php:

Retrieving page #337: 1/statuses/user_timeline.json?user_id=14352786&include_rts=true&include_entities=true&count=200&since_id=344179113302585344&max_id=-1
1 new tweets on this page

Warning:  get_object_vars() expects parameter 1 to be object, array given in /home/earth2marsh/public_html/{myservername}/public/twitter/inc/class.twitterapi.php on line 103

Warning:  Invalid argument supplied for foreach() in /home/earth2marsh/public_html/{myservername}/public/twitter/inc/class.twitterapi.php on line 103

That was after replacing all my files with your fork (excluding config.php). Was there something else required in using your fork?

dasrecht commented 11 years ago

hi there... currently debugging this one

at my place the $tweet array which is handed over while calling

get_object_vars() has following data

array(1) {
  [0]=>
  object(stdClass)#15 (2) {
    ["message"]=>
    string(26) "Could not authenticate you"
    ["code"]=>
    int(32)
  }
}

so i traced this down to the actual url we're passing via twitteroauth.php which gives me back the same error.

@victorjacobs: do you have any idea how to fix this?

dasrecht commented 11 years ago

AH! Gotcha... i'll try this https://github.com/graulund/tweetnest/issues/39#issuecomment-19700356

ali0une commented 11 years ago

@earth2marsh & @dasrecht : you have to make a backup of your tweetnest database first, then download @victorjacobs zip in the link he gave above, unzip it, open your web browser go to tweetnest path/setup.php and follow instructions. Once you are done restore your database backup and enjoy! ; )

graulund commented 11 years ago

@victorjacobs — Thank you so much for your work on this. I'm ready to merge this pull request, but have just one question: Did you accidentally leave your consumer data in the config.php? It seems already filled in...?

victorjacobs commented 11 years ago

@graulund Yeah I left that in so that user's didn't have to get their own key, you can just replace it with your own.

graulund commented 11 years ago

@victorjacobs I'm pretty sure it's frowned upon to leave these keys and secrets in public view. Besides, having one consumer key and secret for everyone is a central point of failure that's not super ideal. So I'm probably gonna put these fields into the Tweet Nest config and ask the user to create these keys themselves. Thanks for all your work though :)

victorjacobs commented 11 years ago

You have a point there, I removed them ;). And any time!

golddave commented 11 years ago

I just installed the latest master. I edited the config.php to include my oauth info (consumer_key, consumer_secret, twitter_token, twitter_token_secr) in addition to my other configuration information. When I run loadtweets.php I get the following message: A Twitter API error occured: Bad Authentication data

Am I missing a step?

graulund commented 11 years ago

@golddave — Did you install the new version of Tweet Nest which includes this? If so, you should go through the process of receiving the Twitter token and secret through the setup page rather than pasting it in manually.

golddave commented 11 years ago

Nevermind. I got it fixed.