On line 213

$val['text'] = $this->EE->security->xss_clean($val['text']);

This line seems to convert the %23 in the hashtag urls back into # characters which breaks the links (You get Twitter's search page instead of search results).

Using EE 2.5.2 and Twitter Timeline 1.4.6.

I noticed that because you have a root folder in your repo that you can't add it as a submodule, as you must create a submodule as a folder.

Thus git submodule add https://github.com/EllisLab/Twitter-Timeline.git system/expressionengine/third_party Twitter_Timeline ends up with system/expressionengine/third_party/Twitter_Timeline/twitter_timeline which then doesn't show up in the modules list.

Unless of course, there is a neat trick unknown to me and SourceTree!

I've implemented this plugin and I've found that when loading 5 tweets not all of them have the urls parsed into links properly.

An example link would be, http://t.co/1StwjK7n

Updated to EE2.5.2 and Timeline 1.4.6 disappeared with line like this
{exp:twitter_timeline screen_name="adamprocter" create_links="user_mentions|hashtags|urls|media" parse="inward"}

But ok like this
{exp:twitter_timeline screen_name="adamprocter" parse="inward"}

removing the create_links makes it work

Hey guys,

I'm running a pretty high-traffic site, and somehow i get this ugly error every now 'n then, which from what I gather from the forums is caused by the amount of requests per hour twitter will accept:

http://www.sandervandoorn.com/

The error:

`A PHP Error was encountered

Severity: Notice

Message: Undefined index: media

Filename: twitter_timeline/pi.twitter_timeline.php

Line Number: 174

A PHP Error was encountered

Severity: Warning

Message: Cannot modify header information - headers already sent by (output started at /home/svdspin/domains/sandervandoorn.com/public_html/system/codeigniter/system/core/Exceptions.php:170)

Filename: core/Common.php

Line Number: 409

Fatal error: ob_start() [ref.outcontrol]: Cannot use output buffering in output buffering display handlers in /home/svdspin/domains/sandervandoorn.com/public_html/system/codeigniter/system/core/Exceptions.php on line 166`

That's a pretty disgraceful way to die for an official plugin...

The relative date tag is too precise, eg "1 month, 3 weeks, 2 days, 12 hours, 2 minutes" - isn't really that useful. Something more along the lines of "About 1 month ago" rather than the current level of precision would be a bit more consistent with what we see elsewhere on the web.