Hello,
I wrote the twitter component and I tested most of the functions and
they worked in my tests.
During development I had problems with authentication because in the
__getAuthHeader function I've used method => 'basic' instead
of method => 'Basic'. After I fixed that authentication worked.

Today I found one bug in the user_show function. The url had one space
at the beginning.
You can fetch the code by cloning the git repository. The repository
url is git://gitorious.org/cakephp-twitter-cpomponent/mainline.git

I've  never got the error you are reporting.
Can you provide some more info about the error. Maybe you are missing
something.

You can see how I use the component in the code of my new blog that
will replace my rails one that is online now.
The code is also on gitorious and you can clone it form
git://gitorious.org/munitic-com-hr/mainline.git

P.S.
You will not be able to run the blog app because there are some files
missing like database.php that I didn't include for obvious reasons :)

Enjoy!
On Apr 16, 6:48 pm, mmayes <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been trying to get the Twitter component working under Cake 1.2
> beta. Whenever I attempt a request that requires authentication, I get
> the error:
>
> Notice (1024): XML cannot be read [CORE/cake/libs/xml.php, line 748]
>
> My username and password are set correctly, and when I access the xml
> page and enter them into the HTTP challenge, it works. But I cannot
> get the component to work other than with methods that do not require
> authentication.
>
> Anybody have any tips? The component I'm referring to it 
> here:http://bakery.cakephp.org/articles/view/twitter-component
>
> Cheers,
> Matt

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to