Thanks Abraham
I'm aware of the difference a doctype would make to *browser*
rendering. Problem is - the info is not for a browser. It's being
passed to another application, that can only take a text response of a
certain size. That means adding all the usual html page headings etc
just won't
I'm aware of the difference a doctype would make to *browser*
rendering. Problem is - the info is not for a browser. It's being
passed to another application, that can only take a text response of a
certain size. That means adding all the usual html page headings etc
just won't work.The
Cameron - you're a star!
That's exactly the bit of magic I needed. Instead of ENcoding it, i
shudda been DEcoding!
Thanks so much.
On 23 Mar, 12:39, Cameron Kaiser spec...@floodgap.com wrote:
I'm aware of the difference a doctype would make to *browser*
rendering. Problem is - the info is
Viewing the http://playercontrol.slevolution.com/twitterupdates.php in
Firefox on OSX it looks fine. In Safari and Opera it is all messed up. It is
possible that by adding a html doctype on your output page the browser will
render it properly. Try looking at it in a few browsers and try adding a
Ok, I use a prewritten Library I picked up somewhere for this one
(altho I have the same problem if i just use PHP/cURL myself).
So here's the main code:
?php
include_once(twitter.lib.php);
$twitterRoot = /LOCATION/OF/CACHE/FILE/;
$user = ;
$pw = ;
$tweetFile =
yikes - hit send before adding thanks :D
On 21 Mar, 16:27, Hippyjim Starbrook hippyjim.starbr...@gmail.com
wrote:
Ok, I use a prewritten Library I picked up somewhere for this one
(altho I have the same problem if i just use PHP/cURL myself).
So here's the main code:
?php
