Is this module supported?

I certainly hope so. The breakdown that occurred on my sites after the Twitter OAuth switch is positively killing me, but unfortunately I'm not smart enough to fix it myself.

The Twitter module, which has worked fine for over a year, stopped working recently and now consistently gives "An error occurred when posting to twitter: 401 Unauthorized". Is this the same problem?

Thanks.

If a maintainer doesn't respond within 2 weeks, advance this issue to the next step in the abandoned modules process.

Marking critical because of number of unresolved issues.

Marking the project as abandoned doesn't resolve the problem for who is using the module and needs it.

Yes, but that's not the point. The point is to warn prospective users of the maintenance status and encourage new maintainers. It enhances transparency and make it more likely that we'll end up with a maintained module.

Subscribing - my impression is that Walkah and Eaton hasn't given up on this project but are discussing solutions to the OAuth issue. If they're not then I'm willing to take part in maintaining the module.

As long as they respond before Sept. 25, then we're fine. Just need to hear from them that this is a current project.

I don't care who does something, but I really hope something happens soon. The Twitter module has become one of the top 5 modules used across all my projects, and right now the wait is killing me.

If nobody has the skills or time why don't all the people who need the module chipin.com to offer up a joint bounty to getting it fixed by somebody commercially?

I only see the Twitter posting facility as a nice to have, rather than critical site component.

hey folks. Yes, it's being maintained. Here's the scoop:

* Twitter's "OAuth-apocalypse" happened a few weeks ago rendering twitter 6.x-2.x unusable (since it used basic auth)
* OAuth module got a rewrite (3.x vs. 2.x) which does not yet work with twitter 6.x-3.x
* There is a twitter_actions patch under review that works with OAuth 2.0.

eaton and I are working to get twitter 3.x working with OAuth 3.x (including actions support). when this is ready, there will be a release.

In the meantime, twitter 6.x-3.x works with Oauth module 6.x-2.02 - you can patch for actions support if necessary.

Apologies for the tardiness, but fixes are forthcoming. Marking this issue as fixed.

re: kiamlaluno (in #6) - I never received such an email. Thanks to heyrocker for pointing me to this issue.

Walkah, thank you! Relieved to see the module is still in progress.

You may want to subscribe to this module's issue queue at http://drupal.org/project/issues/subscribe-mail/twitter?destination=node....

Might be nice to warn people the 2.3 recommended version is not working at all? Took me an hour to get here...

Actually it might be nice to get some feedback at all (what is happening? can a working module be expected in 2010) + the warning. As a tease module users could also be directed to: http://drupal.org/node/404470

There they get info about how they can get their module back to work again (200 posts, hurray!).

Oauth? My customer does not log in via any social network, so they could care less about that. They only want retweets showing up. But I guess what I'm seeing here is that no one cares about the current (allegedly supported) branch? If that's the case, then, indeed, the 2.x branch needs to be marked as unsupported and the 3.x branch promoted (but it hasn't been updated in 8 months either). It would be nice to see some kind of road map posted too.

I spent over an hour searching issue queue before I realized the module is not usable and unsupported.

Please update your module page with that info from your above post. Thanks.

Reverting to prior subject. Twitter maintainers have made many empty promises of updates over the past many months. Please show concrete results--such as at least updating the home page to show that 2.6 is broken and a plan for resolution--or abandon this module so someone else can take it over.

If no response from Twitter maintainers in two weeks, transfer this issue to Drupal.org webmasters project for next step in abandoned modules process.

If the current maintainers do not have time or interest to maintain this module, that is OK! That is not the problem; the problem is that holding on to this module is a roadblock for finding new maintainers who may be willing and able to update this module.

Yes, this module is supported. My sincere apologies for all of the delays sorting things out.

Essentially, the 3.x branch is currently written against the OAuth module's 2.x branch (which is no longer supported). Oauth 3.x is not API compatible and relies on a few modules that are in turn abandoned (and would require twitter module's dependencies to go up by an additional 3 modules). I've been having lots of 'backchannel' discussions about how best to handle this - my apologies for not being more transparent about those.

Of course, all of this is necessitated by twitter's "OAuthpocalypse" which renders the twitter 2.x branch unable to post.

@NancyDru - oauth is not just for twitter signin - it's now required for all protected access (including posting).

In the interim: I have just committed a bunch of the big blocker OAuth-related and will be releasing a new 3.x release - making it the default/recommended release.

Again, sorry for all the delays.

For the record:

The 3.x version of OAuth.module does not depend on any abandoned modules.

Regarding the 3.x version of OAuth.module having too many dependencies - it's true that one of the three dependencies isn't entirely necessary (the inputstream one) but the other two dependencies are such that many sites probably already have them activated anyway (Chaos tools and Autoload).

These are no show stoppers at all and I'll help with any changes on the OAuth module needed to get the Twitter module upgraded.

@voxpelli thanks for the correction. you're absolutely right. Moving to OAuth - 3.x is in the plan.

Thank you, @walkah!

@Walkah: We do not sign in to, or from, Twitter; the only thing we do is to show the little tweet count block and retrieve tweets to display for the user. What we really need right now is retweets (#867906: Ability to show full public feed with retweets).