Twitter returned an error: Not Found

I have the same problem. I think API Twitter has changed this night.

I've resolved the problem installing development version and editting the file twitter.lib.php. Change 'api.twitter.com' in line 17 to 'api.twitter.com/1'. I've found support information here: https://dev.twitter.com/discussions/10803

"All non-versioned API endpoints will go away. Though you may occasionally find these endpoints responding as we ramp down, expect them to be gone in two weeks. This list includes:

All API endpoints on www.twitter.com and twitter.com.
Endpoints on api.twitter.com without /1, /1.1 or /oauth in the fully qualified URL."

I was getting the same error, and on retrying to add the app I get the following error Twitter returned an error: Not Found and similar error to you in my logs

#1 didn't fix the problem for me unfortunately...

p.s. in twitter.module on line 10 api.twitter.com is also listed.

Thanks @digibeetle! I've changed the line 10 in twitter.module but nothing happens, my news are also posted since I edited the file twitter.lib.php...

This hack works with version 6.x-3.x-dev

digibeetle, I already found a workaround to add/re-add an account. You need to add manually into the database. All info which data to add can be found in dev.twitter.com/apps.

Hope this solved your problem.

digibeetle, I already found a workaround to add/re-add an account. You need to add manually into the database. All info which data to add can be found in dev.twitter.com/apps.

Can you explain a bit more in detail?

Which Table? twitter_account?

Hey guys, I think the 7.x issue might help someone - adding the /1 in the api url helps for some things, but you don't want to apply that to oauth requests. It may help to backport the patch I wrote for a resolution:
#1809720: On cron: Unexpected error: Sorry, that page does not exist

#1 worked for me

Don't modify 'api' => 'api.twitter.com', because the users cannot add/update their Twitter account.

# 16 works for me and posting and authorization. Thank you!

#1 worked for importing statuses:

Change 'api.twitter.com' in line 17 to 'api.twitter.com/1'

#16 worked for posting but not without some figuring out:


protected function create_url($path, $format = NULL) {
if (is_null($format)) {
$format = $this->format;
}
$conf = TwitterConf::instance();
/* Replace this section
$url = 'http://'. $conf->get('api') .'/'. $path;
if (!empty($format)) {
$url .= '.'. $this->format;
}
return $url;
*/
/* with hack from http://drupal.org/node/1809648#comment-6593224 */
switch ($path) {
case 'users/show':
case 'statuses/update':
$url = 'http://'. $conf->get('api') .'/1/'. $path;
break;
default:
$url = 'http://'. $conf->get('api') .'/'. $path;

}
//
if (!empty($format)) {
$url .= '.'. $this->format;
}
return $url;
}
}

and because my RSS URL was broken, I found : https://dev.twitter.com/discussions/844

https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=decibel...

well, not sure that is workable with the 6.x-3.0-beta9 version that is in use so here's a patch for that

#24

that code change works WITHOUT the #1 Change 'api.twitter.com' in line 17 to 'api.twitter.com/1'

here's the new patch against the 6.x-3.0-beta9 code

I rerolled the patch and tested it against a fresh copy of 6.x-3.0-beta9

part of the problem here is that version is not a branch in the project repository, so you need to download the tarball, extract it, make it a local repository THEN you can apply this patch

#26
Try to flush all cached data.

Update - change double quotes to single quotes.

#31 basically worked for me, but I checked out the dev branch (6.x-3.x) and rerolled the patch there, since this is generally were patches get rolled from and applied to since it typically contains the most recent development.

I'm attaching my version against the dev branch.

@CrackWilding: I'm just getting statuses as well and I had no problems.
- First I suggest checking out the dev branch and applying the patch there, since my direct experience with that was successful
- How are you getting the statuses? You're just running cron right? That's the only place I know of that fires the function.
- Make sure you reversed changes from #1 if you applied them and start from a clean checkout of the code.
- Are you still seeing errors in your watchdog log? If not, make sure you have importing enabled at admin/settings/twitter and on the user's twitter account settings page.

It doesn't work for me. 6.x-3.0-beta9 The error is gone but still no post to twitter with the patch #27. The dev version even doesn't work.
:-(

#1's solution works fine and you don't need to install the dev version as well. (atleast I didn't). All I did was, open the file twitter.lib.php. Change 'api.twitter.com' in line 17 to 'api.twitter.com/1' and save it. actually u can chk ur twitter dev account, dev.twitter.com/apps and goto ur app and click on the OAuth tool tab and chk the 'Request URL' it should be like, https://api.twitter.com/1/ where in the line 17 of the twitter.lib.php file, its missing the /1 part. *DONOT enter '/1/' rather ignore the last '/' and use '/1'.

Marking duplicate of #1814610: Use proper API URLs

#16 worked for me too using patch in #31!

Please stop using patch #16, the fix has already been committed.

#1814610: Use proper API URLs

Hi i am very new to this Twitter OAuth things. Please let me know how we can get all this below mentioned values.

I am using this all modules like:-
1) oauth, 2) twitter, autoload etc.....

But i am only getting these 2 values rest of are not getting.
[oauth_token:protected] => 46057862-oXyEEHV8urFCNWWvNClzlDfXx8FQvAzjn2kFapGyK
[oauth_token_secret:protected] => 1BS53iZ9w9Xqe4qZwWloVXgqmrNcDvZhOuA3qaaPyg

TwitterUser Object
(
[id] => 0
[screen_name] =>
[name] =>
[location] =>
[description] =>
[followers_count] => 0
[friends_count] => 0
[statuses_count] => 0
[favourites_count] => 0
[url] =>
[protected] => 0
[profile_image_url] =>
[profile_background_color] =>
[profile_text_color] =>
[profile_link_color] =>
[profile_sidebar_fill_color] =>
[profile_sidebar_border_color] =>
[profile_background_image_url] =>
[profile_background_tile] => 1
[verified] => 1
[created_at] =>
[created_time] =>
[utc_offset] => 0
[status] =>
[oauth_token:protected] => 46057862-oXyEEHV8urFCNWWvNClzlDfXx8FQvAzjn2kFapGyK
[oauth_token_secret:protected] => 1BS53iZ9w9Xqe4qZwWloVXgqmrNcDvZhOuA3qaaPyg
[uid] => 1
[import] => 1
[include_retweets] => 0
[is_global] => 0
)

Updating to the 6.x.3.x-dev version, which includes the patch mentioned above, did not make my site work again. Looking at the modules-list, I noticed that this version of the twitter-module requires the oauth_common module, which was missing. After I updated the oauth-module to the most recent version (http://drupal.org/node/1022152), the twitter-module started working again. Hope this helps anyone.

@#48 decibel.places:
The 6.x-3.x-dev download is right on the front on the project page, there is no need to concern yourself with git at this point - once a patch is committed to a dev branch, an updated download will appear within 12 hours or so, and we are much past that now.

Also, releases in Drupal/git are typically done with tags, not branches - so you start with the 6.x-3.x branch and then look for the correspodning beta9 tag in that branch - but again if you are generating a patch to be applied for a future release, it is usually best to work from the dev branch (6.x-3.x) which has the most current development and will ultimately become the next release.

@jkiff re #50
try the 6.x-3.x-dev version, maintainer says it is working (perhaps with an update to Oauth module as a depenency)
also patch 23 was an early version, I rolled an update that has been corrected for code standards later in this thread

@justindodge re #49
I checked out the repo and 6.x-3.0-beta9 is NOT available in it, as a tag
Users of the 6.x version of this module are aware that 6.x-3.0-beta9 was released ahead of an update to to the -dev branch, that is why this thread references that version

I get when posting with #16

Fatal error: Class 'TwitterConf' not found in /home

@decibel .. I did disable, uninstall and delete the beta9 version. I then re-uploaded and enabled the dev version however it still shows as beta9 for the version on my modules page. I'm assuming I am now using the dev version but this it should be reflected properly on the modules page. Am I doing something incorrectly?

To sum up I've tried both versions while ensuring the api is pointing to api.twitter.com/1 in both cases and i still get twitter not found.

@jkiff re: #55

did you clear the Drupal caches? (on Performance page, using Drush, or admin menu)

I've tried the dev version, enabled oauth autolaod and now I'm ending in a with screen of death...
:-((((((((((((((((((((

I had the same issue, and upgrading the Twitter module to 6.x-3.0 version released on 2012-Oct-27 was just the first step...

The 6.x-3.0 version of the Twitter module seems to require an upgrade to the OAuth 6.x-3.0-beta4 version released on 2011-Apr-06 (it just silently failed while still using OAuth 6.x-2.02), but this is a major re-work of the module from 6.x-2.02 and the only way I could get it to install properly was to completely uninstall the previous OAuth module and install this version from scratch.

Only after doing all of these steps can I now post to Twitter again as I could before Twitter changed its API. Just upgrading the Twitter module to 6.x-3.0 was not enough.

So, Twitter changes its API without warning or any notification that I saw, the Twitter module doesn't mention this dependency on the new OAuth version, and the OAuth module has no upgrade documentation that I can see, just warnings that it was a major refactoring in its release notes. Things are working now, but it seems like this could have been clearer at each step. Maybe I've just become spoiled, I guess I normally don't have to use my brain this much.

At the very least, I am really grateful that the Twitter module maintainers updated the module in what seems like a pretty reasonable amount of time. Thanks guys!

I can confirm #61 is right.

Uninstall both Oauth and Twitter modules. Upgrade to OAuth 6.x-3.0-beta4 and Twitter 6.x-3.x-dev. You could try Twitter 6.x-3.0 but I went with the dev version instead. Enable the modules and you won't see the error message anymore.

I haven't tested if it works as before. Will give it a try (hopefully) soon and update here.

Working for me on Twitter 6.x-3.0-beta9 w/ OAuth 6.x-3.0-beta4

I needed to hack the Twitter.lib.php to add in the API version to the url in the create_url method. Without it, TwitterException was thrown and also ran into #1383992: Error when adding an account: PDO Exception: Integrity constraint violation in twitter_account_save(). This is for no oauth, just pulling statuses and in 7.x-3.x branch.

Oh, crap. I hate when drush fails to update. I thought I had completed the update last night. Sorry.