I think it could be the OAuth classs now because of a recent error but
it does not seem to work when I put it in an array either.
Furthermore this is the class that Twitter directly links to from the
API Wiki under PHP examples... If it is this buggy (if in fact it does
not work even as an array
I did try putting it in the array but only did one more quick test. I
will have to try it again. I am pretty sure from the limited amount of
documentation that the array holds post values for when you make a
POST api call.
If the OAuth class is this buggy (given that the array is the issue
and I
are you sure they're not returned via the script? did you dump the data you
received using wireshark or some other network monitoring tool? it could be
that the $oauth class is simply not parsing it correctly.
On Tue, Oct 27, 2009 at 11:31, TylerC tyle...@gmail.com wrote:
I really don't get it
Its the standard OAuth class provided from the Twitter wiki...
When I dump it, even with var dump or print it begins with :
?xml version=1.0 encoding=UTF-8?
users type=array
But then right after the /users tag the data ends. Its very odd and
its driving me nuts.
On Oct 27, 1:40 pm, JDG
The cursor stuff is still somewhat new. Just because it's on the wiki
doesn't mean it was provided by Twitter (it's not). It may not have been
updated to handle cursors. You should do a dump via a network monitoring
tool, like wireshark or even just curl, to see what's sent to the oAuth
class. I
Idk the OAuth files just return all the data from the CURL query there
is not any parsing done to it from what I can see. It just gives you
whatever it gets from Twitter which leads me to believe I am missing
some kind of parameter or there is a bug with the API and OAuth.
On Oct 27, 1:46 pm,
Further moor I edited the OAuth script for some debugging and output
the exact string returned by the CURL call and there is still no
next_cursor showing up.
On Oct 27, 1:52 pm, TylerC tyle...@gmail.com wrote:
Idk the OAuth files just return all the data from the CURL query there
is not any
then you should open a bug against twitter.
On Tue, Oct 27, 2009 at 13:32, TylerC tyle...@gmail.com wrote:
Further moor I edited the OAuth script for some debugging and output
the exact string returned by the CURL call and there is still no
next_cursor showing up.
On Oct 27, 1:52 pm,
Are you sure that's where the cursor=-1 is supposed to go? Isn't the
array meant to contain all the options you want to pass? Perhaps your
library is cleaning up your URL to make sure it has no request
parameters and only passing the parameters in the array that you're
passing as a 2nd
I also recommend using Wireshark, tcpdump or the like to get an
authoritative picture of what’s happening. And if there is indeed a
bug, the output serves as clear proof.
10 matches
Mail list logo
