Since version 1 is marked as deprecated.

https://dev.twitter.com/docs/api

Since version 1 of the API will cease working soon, we will not create a new branch.

Comments

juampynr’s picture

Oops, I did not take long in changing my mind.

I will work on branch 7.x-4.x as this branch loads the Twitter library using Libraries module, which is a great strategy to share the library and reduce our maintenance time as there is only one library to maintain and not one per branch.

http://drupal.org/project/libraries

juampynr’s picture

juampynr’s picture

I have implemented most of the API endpoints at https://github.com/juampy72/twitter-rest-php/commits/master.

TwitterOAuth class has been merged into Twitter class, as now OAuth is mandatory.

Since tomorrow I will start reviewing the code so it uses the new library. The fact that OAuth is mandatory is great because it simplifies considerable the module's logic.

juampynr’s picture

Managed to add accounts with the new library. Now I will move on to pull tweets.

juampynr’s picture

And Tweets are also being pulled in correctly :D

juampynr’s picture

Version: 7.x-3.x-dev » 7.x-4.x-dev
Status: Active » Fixed

Reviewed all sub modules. Main logic of the module works correctly using the 1.1 REST API.

juampynr’s picture

Version: 7.x-4.x-dev » 6.x-3.x-dev
Status: Fixed » Active

Backporting to 6.x-4.x. Created and pushed the branch although it is not visible yet at the version form field.

juampynr’s picture

Version: 6.x-3.x-dev » 6.x-4.x-dev

Updated logic to add Twitter accounts and list tweets.

juampynr’s picture

The 6.x-4.x branch is almost ready. I could not make Rules integration to work completely but I think it is an issue with Rules rather than with the Twitter API.

volresource’s picture

Thank you for this work. I couldn't get v6.x-3.0 to work, after finally upgrading from the beta (6.x-3.0-beta6). But 4 beta1 did!

I try to avoid betas, but there you go. On first installing 4 beta1, the user twitter account seemed to have disappeared, I think this was a server glitch but I was fooled by the lack of 'twitter post success' message - switched off the modules before checking the twitter account and noticing that the test post HAD worked.

Is there any chance you can get the 'twitter success' message to be meaningful - it had been giving this message despite failure since the last success using 3.0 beta6 back on 9 Oct 2012.

Thanks again.

juampynr’s picture

@volresource, please create a specific issue with your problem. This issues is just to track the upgrade of the REST API that the module uses.

juampynr’s picture

Status: Active » Fixed

Marking this as fixed. I will create a bug for the pending bug at 6.x-4.x and then this is ready to be released.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.