laouran

Gone a few days and i’m in version 0.5.13 !
It’s all good for me too.
Excellent !!

Back on my site today, i find out characters were bad again… arg !

So, i manage to get it right by bypassing our utf8_encode…
Seems that the tweets were in utf8, and don’t even need a htmlspecialchars !
( I don’t have time to fully understand the whole thing, but i bet it’s work through json_encode witch compute only utf8 data. )

Looking around, i found this : http://www.phpriot.com/articles/php-twitter-api-screencast
So a i had a final htmlspecialchars() function after, just in case.

so :

// Encode Special Chars
 //   $tweet->text = utf8_encode($tweet->text);  // no need
 $tweet->text =  htmlspecialchars($tweet->text ) ;// just in case !

hope it helps.

I think i get abuse by transient/cache , i only need the htmlspecialchars transformation. ( removing htmlentities )