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

Loadtweets Not Loading Tweets #49

Closed golddave closed 11 years ago

golddave commented 11 years ago

Tweets have not been loading the last few days. At first I thought it was an API issue (with Twitter shutting down the 1.0 API) so I changed all references to the API in loadtweets.php to 1.1 but that didn't fix things. The current error I'm getting when I run loadtweets is as follows (with the id changed):

Retrieving page #1: 1/statuses/user_timeline.json?user_id=XXXXXXXX&include_rts=true&include_entities=true&count=200&since_id=344449689871081472 1 new tweets on this page

Warning: get_object_vars() expects parameter 1 to be object, array given in /home/golddave/public_html/tweetnest/inc/class.twitterapi.php on line 103

Warning: Invalid argument supplied for foreach() in /home/golddave/public_html/tweetnest/inc/class.twitterapi.php on line 103

The same issue occurs when loadtweets is referring to either the 1.0 or 1.1 version of te Twitter API.

jeherve commented 11 years ago

That's indeed caused by the changes to the REST API, and I'm afraid there is more to be done than just changing 1 to 1.1. See #39 for more discussion about this.

ghost commented 11 years ago

Yes, we need to do more than changing 1 to 1.1.

At linux shell, typing it (for example):

~# curl https://api.twitter.com/1.1/users/show.json?screen_name=Graulund

We get:

{"errors":[{"message":"Bad Authentication data","code":215}]}

Twitter API Documentation says: "Authentication required on all endpoints In version 1.1, we're requiring applications to authenticate all of their requests with OAuth 1.0a or Application-only authentication. Not only will this visibility allow us to prevent abusive behavior, but it will also help us to further understand how categories of applications are using the API. We'll apply that understanding to better meet the needs of developers as we continue to evolve the platform. At this time, all authentication requires user context, but in the coming weeks we'll be pushing out support for a form of authentication not requiring a user context."

Sources:

graulund commented 11 years ago

Duplicate of #39