1) After the changes to Twitter and its full move to API 1.1 that requires OAuth, I noticed a lot of the feeds on my sites where breaking. I used to just use simple json to get the feed. After some research, I created a php script (here: https://github.com/bobbydank/my-twitter-1.1-api-function) that did the same thing as before, just used OAuth codes. I have had some good feedback on the function, and I decided to expand it into a module.

This module creates a block that requires Twitter OAuth codes from the Twitter's own 1.1 API and returns a simple unordered HTML list that can be styled in the sites theme css. The user has the ability to get whatever feed they wish based on the username and the number of tweets they wish to return.

2) screen shot: http://catchylabs.com/sites/default/files/Screen%20Shot%202013-07-18%20a...
Link to web page: http://catchylabs.com/drupal/simple-twitter-feed

3) link to project page: https://drupal.org/sandbox/bobbydank/2045997

4) git repository: git clone --branch master bobbydank@git.drupal.org:sandbox/bobbydank/2045997.git

Comments

ayesh’s picture

ayesh commented

Welcome!
I found some similar attempts for the same task:
- https://drupal.org/sandbox/craigweb/1818578 / https://drupal.org/node/1818974
- https://drupal.org/project/twitter_block
Could you explain how your module is different from the others ?

There are multiple changes required before your code being compatible with Drupal Coding Standards: http://ventral.org/pareview/httpgitdrupalorgsandboxbobbydank2045997git

Some other points

(I'm not going to mention branch name and file name changes that are already covered in the ventral.org report).
- You will probably need to check if the server has curl installed before using it (to prevent fatal errors).
- Consider moving the hardcoded html div/span set to a template file, simple-twitter-feed-item.tpl.php for example so users can have better control over the themable output.
- You need to unset all variables set by your module in a hook_uninstall implementation. Also, consider using an array of options to store the values. You can variable_set() an array, and when you variable_get(), it will be unserialized for you automatically.

ayesh’s picture

ayesh commented
Status: Needs work » Needs review
ayesh’s picture

ayesh commented
Status: Needs review » Needs work

There are some blockers in the ventral.org report so I'm setting the status to "Needs work" until you get them fixed. Thank you for your hard work, specially in the great documentation anyway.

PA robot’s picture

PA robot commented
Status: Needs review » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.