EE Twitter Search

Mine stopped working some weeks ago as well. I suspect twitter changed their API and the plugin hasn’t been updated to accommodate.

Awesome plugin Lumis. I have been using it without problem for a few weeks- but today it has been blank all day.
Is there anyway the plugin could cache if it is at API limit or cant get more results for any reason?
Also- is there a way to push the limit beyond 100?

Thanks, David

Thx Lumis - awesome plugin!!

I am trying to pass in

{exp:search:keywords}

as a twitter search parameter for

{exp:twitter_search:find q="{exp:search:keywords}"}

but it’s not working for me - is this supported? Could you suggest another way to do this.

I would like to give my site’s visitors results from both my site and twitter for their searches.

Thanks

Thx Lumis - awesome plugin!! I am trying to pass in

{exp:search:keywords}

as a twitter search parameter for

{exp:twitter_search:find q="{exp:search:keywords}"}

but it’s not working for me - is this supported? Could you suggest another way to do this. I would like to give my site’s visitors results from both my site and twitter for their searches. Thanks

Done it

{embed="my_embedded_twitter_search_template" twitter_search_tags="{exp:search:keywords}"}

just used an embedded template and parsed in the search keywords as an embedded variable.

Hey this plugin is freaking awesome. Thanks!

I’m having trouble getting the if no_results conditional to work though. Is there something wrong with my code?

{exp:twitter_search:find phrase="{twitter-rss}" rpp="7" convert_url="yes" cache="yes" refresh="5" word_censoring="off"}
                            <div class="tweet">
                                {profile_image_url}
                                {text}
                                from {from_user} — {relative_date} ago
                            </div>
                            {if no_results}Sorry, there's no noise about this band on Twitter! {/if}
                            
                            {/exp:twitter_search:find}

We too are having the same issue. from:dabbledoo does not return anything q=”from:dabbledoo”

thanks!

When Twitter Search is installed, has anyone run into this PHP notice:

Notice: Undefined property: stdClass::$results in /…/system/plugins/pi.twitter_search.php on line 67

The plugin shouldn’t even be called when this error pops up. The plugin code is on the template, but should only fire is segment_2 has something in it.

Hey Ryan -

Yes, I got that on a client’s site yesterday. I would imagine it is checking on every page load if the cache has expired. When I was getting this error, I did the same search on Twitter and it looked like the search was performing as expected. I’m wondering if it has something to do with Twitter’s Search API call limit - since they limit by IP. Not sure though.

If you or anyone figures something out, please let us know!

Thanks,

Doug

Side note: I feel as though maybe when the plugin / twitter throw errors, it should not invalidate the locally cached entries. That way if it cannot connect or does not receive any results back from Twitter, it will not break the site.

I just added an “@” to the beginning of line 67 I can’t have that error showing on the client site. Seems to work.

@$this->eventdata = $this->jsondata->results;

We too are having the same issue. from:dabbledoo does not return anything q=”from:dabbledoo”

I’m having the same problem. Sometimes when doing a from:username search I get nothing back. Then a half hour later it’ll work again. Does anyone know what is causing this?

Also, how can I display something if there were no results? I tried total_results but it didn’t work.

Thanks.

There is no {total_results} in this plugin. Nor is there currently a {count}. It really could use both.

There is no {total_results} in this plugin. Nor is there currently a {count}. It really could use both.

I agree, that would be nice. Especially if sometimes it doesn’t give any results (because Twitter API is down perhaps?) I’d like to display a message.

I’m pretty convinced the error has something to do with Twitter limiting (throttling) the number of requests we hit them with. The only thing is I had it installed on a low-traffic site that couldn’t possibly have been going over Twitters limit. You guys wouldn’t by chance be using EngineHosting for your projects, could you? If so, then maybe our requests are hitting Twitter’s search API from the same IP… (now I’m just making up conspiracy theories).

Anyways, I ditched the Twitter Search plugin and went with Twitter Timeline instead. All I had to do was display entries from 3 accounts, so I just created a new account, followed those 3 accounts, and hooked Twitter Timeline up to that new account. Creative - I know. 😊