404: {"errors":[{"message":"Sorry, that page does not exist","code":34}]}

katak_kembong · 2012-10-31T04:03:00.000Z

still not working
last month there is no prob.

$c = curl_init();
curl_setopt($c, CURLOPT_CAINFO, $ca);
curl_setopt($c, CURLOPT_SSL_VERIFYPEER, FALSE);

//curl_setopt( $c, CURLOPT_URL, “http://twitter.com/statuses/user_timeline/plustrafik.xml?callback=twitterCallback2&count=25”);
curl_setopt( $c, CURLOPT_URL, “http://twitter.com/statuses/1.1/user_timeline/plustrafik.xml?callback=twitterCallback2 count=25”);

curl_setopt( $c, CURLOPT_HEADER, 1 );
curl_setopt( $c, CURLOPT_RETURNTRANSFER,1);
curl_setopt( $c, CURLOPT_TIMEOUT, 60 );

$response = curl_exec( $c );
$responseInfo = curl_getinfo($c);

echo curl_error($c);
curl_close( $c );

$my_file = ‘tweet.xml’;
$file = fopen("$my_file", “w+”) or die('Cannot open file: '.$my_file);// w-write,r-read, a-append);
$new_data =serialize ($response). “\r\n”; // saya add code serialize // http://php.net/manual/en/function.serialize.php
fwrite($file, $new_data);
print “Data Written”;
fclose($file);

episod · 2012-10-31T14:26:16.000Z

You’ll need to more work than just change the URL to make this work with API v1.1 – API v1.1 requires OAuth authentication for this method. You’ll also need to use the api subdomain. And the JSON output format, as XML is not supported in API v1.1.

kevinbrou · 2012-11-02T16:54:29.000Z

Thanks for that information, I was having a similar issue on all of the sites I use the call back.

mybiccies · 2012-11-03T23:25:00.000Z

Can somebody help me fix this code please? Currently I’m using:- which returns:- twittercallback2({“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]});

I understand changes have been made but I’m not experienced enough to know what that change is exactly. The twitter feed on www.biccies.com isn’t working as a result.

Any help would be gratefully received.

episod · 2012-11-05T15:45:33.000Z

You probably have some code somewhere that looks like this:

Instead of that, it should look like this:

But you should also know that loading tweets this way will no longer be possible after March 2013. We recommend using our Embedded Timeline widgets instead.

zackron · 2012-11-08T04:59:00.000Z

Hi guys… I’m also getting an error code 34… I’m using api.twitter.com and the 1.1 API version… here is the URL that is being called: https://api.twitter.com/1.1/search/tweats.json?count=25&q=%24EURUSD&result_type=recent - I’m not 100% sure that I’m calculating / sending the OAuth stuff correctly in the authorization: request header… but I’m assuming that if there were any problems with that, it would generate some error other than the code 34, right?

Thanks.

episod · 2012-11-08T14:57:47.000Z

Verify that you’ve got that path right – I see “tweats” in that path instead of “tweets”

zackron · 2012-11-08T22:25:04.000Z

Great catch @episod, thanks! I don’t know if I still had Halloween treats on the brain or what, but that was the problem.

dustin2k · 2012-12-01T03:29:05.000Z

Thanks jerry. This was my issue as well, after fixing the api.* prefixes.

MarathonKruse · 2012-12-02T04:40:00.000Z

I feel like I must be missing something obvious with this, but I, too, am having issues with the code 34 error:


$friends_str = implode(',',$friends_ids_all);
$conn2->request('POST',$conn2->url("https://api.twitter.com/1.1/users/lookup.json?user_id=$friends_str&include_entities=true"));

ReDetection · 2012-12-17T08:11:00.000Z

I’m getting code = 23 message = “Sorry, that page does not exist” on https://api.twitter.com/1.1/users/lookup.json too! Everything else works fine.

vis_1321 · 2013-01-09T05:50:00.000Z

Get ing error {“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}
while using http://api.twitter.com/1.1/users/show.json api.
with every other api works well but while using this get error every time

episod · 2013-01-09T16:09:26.000Z

Are you providing a user id or screen_name belonging to a user that does not exist?

James_Snell · 2013-01-10T13:03:31.000Z

Hello

I am getting the same issue when adding / removing tweets from favorites. It seems fine for some tweets and not others.

404:The URI requested is invalid or the resource requested, such as a user, does not exist.
{“errors”:[{“message”:“Sorry, that page does not exist”,“code”:34}]}

Any ideas?

James

James_Snell · 2013-01-10T19:40:33.000Z

To confirm above, I am passing ID’s which are on my home timeline so the ID’s definitely exist. I am also definitely passing a valid oAuth token as I am using it on GET calls successfully and some of the POST calls to work

AbdullahFaqeir · 2013-01-16T08:37:13.000Z

I had the same issue with /1/ but I’ve changed it to /1.1/ and it works just fine

akmaurya31 · 2013-01-18T18:50:20.000Z

Sir Please HELP ME

deividfortuna · 2013-02-18T21:07:29.000Z

I used the same code and don’t work. I don’t know what to do more.

ManishSingh_vns · 2013-02-19T16:31:00.000Z

hi i am getting 404 error in account/verify_credentials.json request after access token returned from oauth/access_token

Pls help…

jayaprakash1313 · 2013-02-22T15:21:28.000Z

Hi,
I need to parse twitter home feeds. So can any one help.Which is the correct parsing method (.XML,.JSON) and give the Url.Ex(home_timeline) not User_timeline.
What i post and what my followers post.