I'm attempting to pull tweets in with a specific hashtag, and have been lucky enough to stumble upon this article;

http://thereisamoduleforthat.com/content/consuming-new-twitter-11-api-feeds-and-friends

infojunkie was gracious enough to attach a feature and instructions at the bottom of the post, and receive the following errors when I enable those modules and dependencies.

Notice: Undefined index: table in view->fix_missing_relationships() (line 617 of /home/aaronis/public_html/cwvtweets/sites/all/modules/views/includes/view.inc).
Notice: Undefined index: table in view->fix_missing_relationships() (line 617 of /home/aaronis/public_html/cwvtweets/sites/all/modules/views/includes/view.inc).

Copying my consumer key and secret into the OAuth Fetcher work without error.

When I create a new node of type 'Twitter Feed' with a Title of 'Drupal' and a Feed URL of 'https://api.twitter.com/1.1/search/tweets.json?q=%23drupal' I receive the following error;

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /cwvtweets/batch?render=overlay&id=11&op=do StatusText: Internal Server Error ResponseText:

Screen Capture

I also periodically receive a warning message stating;

"Could not find OAuth access tokens for site twitter. You should probably authenticate first to access protected information."

Any ideas on why I'm receiving all of these errors?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

aaron.silber’s picture

Assigned: aaron.silber » Unassigned
infojunkie’s picture

Can you please paste your web server error log? The screenshot you attached shows it's a PHP error that occurred.

aaron.silber’s picture

Just checked my PHP error log and it's clean. I've thrown some errors just to make sure.

I just ran through the whole process again with a fresh Drupal install and documented two other errors as well.

'error_enTwitterfeed.png' occured directly after enabling the twitter_feed-7.x-0.1.tar module
'error_drupalview.png' occured while first accessing the #drupal view.

infojunkie’s picture

It's not immediately apparent what the trouble could be. I'll try on a plain Drupal install and report back here.

In the mean time, please check the Drupal log for additional clues.

infojunkie’s picture

I've found the source of the errors above. There was a bug in the Views Auto-Refresh module, so please upgrade your version with the latest 7.x-1.x-dev. Also, I've updated the twitter_feed feature on my blog post, so please try the latest version.

infojunkie’s picture

However, the bug I found in #5 only affects the view that's included in the feature. The feed importer is not affected, and before going on to debug it to find why import is failing, please make sure you've correctly installed the Feeds OAuth dependencies, as explained on the module page.

aaron.silber’s picture

After installing the updated twitter_feed feature, updating Views Auto-Refresh, and double checking my Feeds OAuth dependencies I'm able to import Tweets.

I'm thrilled that this is working now. I noticed that the view pointing at '/twitter' isn't auto-refreshing and suppose it's because the "header of type Global: Autorefresh" is missing from the view in the feature - though the method listed here (https://drupal.org/project/views_autorefresh) describing the ping script sounds like a better solution.

I supposed I'll also need to setup a cron job to import more frequently than Drupal's lowest default of "1 hour".

I'm dabbling in this as part of a side project with some friends and really appreciate your help.
Is your Amazon wishlist up to date?

infojunkie’s picture

The updated twitter_feed feature *should* correctly include the auto-refresh header. But you'll also need to include the ping script that I just uploaded to the post - sorry for missing this. I updated the instructions for installation. For good measure, make sure you're using the Views Auto-Refresh 7.x-1.x-dev version dated June 24th (or later).

Yes, my Amazon wish list is up to date :-) Thanks!

infojunkie’s picture

Status: Active » Fixed

Can we mark this as fixed?

aaron.silber’s picture

Yes.

Status: Fixed » Closed (fixed)

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

tinohuda’s picture

Sorry for re-open,

tinohuda’s picture

Issue summary: View changes
Status: Closed (fixed) » Active

Sorry for re-open,

I use the latest views_autorefresh and use file attached here: http://thereisamoduleforthat.com/content/consuming-new-twitter-11-api-fe...

But i have the error message like this: "We tried hard, but did not get a request/temp token from the server."

I was create new API key and update at HTTP OAuth fetcher setting, clear cache also.

please assist me.

Thanks.

infojunkie’s picture

You might have to recreate the feed importer manually - the one in the post might be obsolete.

tinohuda’s picture

FileSize
62.75 KB
9.59 KB

Hi again,

1.
i'm stuck on OAuthHTTPFetcher settings, i use oauth 1.

when i click authenticate I got wrong message:

"Failed to parse HTTP response: No HTTP/ found."

here's my image setting attached. please assist and thanks before.

2. I cannot download http://thereisamoduleforthat.com/sites/default/files/ping.php_.txt
it's forbidden.

infojunkie’s picture

@tinohuda - fixed (2) forbidden file. I will diagnose (1) when I get some time.

tinohuda’s picture

thank you. downloading now(2), but (1), error still occured.