I just tried posting from another server and it worked just fine!
*grrr*
So I guess that means there's something going on with my server and
the cURL install, maybe? Can someone try pointing me in the right
direction to see if I can get this corrected? (No sense in having a
development server if
was that the problem? I ran a test with that script under a few different
accounts and it was working fine. Did you try posting from another server?
On Tue, May 12, 2009 at 4:38 PM, Yazmin wrote:
>
> Oh no worries. I appreciate you asking regardless.
>
> I did read about the status not getting p
Oh no worries. I appreciate you asking regardless.
I did read about the status not getting posted if it was the same, so
while I was doing these tests, I would go back to the Twitter account
and delete the duplicate status, or change the value of the status
text that I was posting.
On May 12, 6:
I just have to double check this but are you absolutely certain the status
is getting posted? If you are posting with the same text as the previous
status it gets discarded. Double check the timestamp of the last post.
Sorry. Had to ask the "is it plugged in question".
On Tue, May 12, 2009 at 17:0
Thank you. I'm not even sure what to do with that. I'm looking at this
class and there are no other curl requests getting executed but the
ones I posted. (Obviously that must not be the case since we *know*
that a successful updated returns 200, but right now I'm just not
seeing it where this clas
Well this leads me to believe that the var_dumps are somehow getting called
on a curl request other then the one posting the status update.
CURLINFO_HTTP_CODE should only return int(200) when an update is successful.
On Tue, May 12, 2009 at 15:49, Yazmin wrote:
>
> That returned:
>
> int(0)
>
>
That returned:
int(0)
I also checked the Twitter account and I see the new status updated.
On May 12, 4:35 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Can you verify that the update is actually getting posted to twitter.com and
> var_dump(curl_getinfo($ch, CURLINFO_HTTP_CODE))
>
>
>
> On
Can you verify that the update is actually getting posted to twitter.com and
var_dump(curl_getinfo($ch, CURLINFO_HTTP_CODE))
On Tue, May 12, 2009 at 15:19, Yazmin wrote:
>
> A var_dump($data) produces:
>
> bool(false)
>
> If I add:
>
>$Headers = curl_getinfo($ch);
>var_dump($Hea
A var_dump($data) produces:
bool(false)
If I add:
$Headers = curl_getinfo($ch);
var_dump($Headers);
A var_dump($Headers) produces:
array(19) {
["url"]=>
string(59) "http://twitter.com/statuses/update.xml?status=testing
+1+2+3"
["http_code"]=>
int(0)
["header_size"]=>
What do you get if you add:
var_dump($data);
On Tue, May 12, 2009 at 14:05, Yazmin wrote:
>
> Sadly I need more clarification...and possibly a code example.
>
> Using PHP, I know that I can successfully get a feed of a user's
> latest statuses using this code:
>
>$ch = curl_init
Hello,
This does not directly answer your question, but I think it will help you
with many things. I would suggest using the class twitterPHP (
http://twitter.slawcup.com/twitter.class.phps) and execute cURL through the
class, that way you wont have many cURL calls. Just a suggestion.
On Tue, May
Sadly I need more clarification...and possibly a code example.
Using PHP, I know that I can successfully get a feed of a user's
latest statuses using this code:
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_RETURN
Oh thanks! I misunderstood what was getting returned to me by the
update. I see it now that you mentioned it. :)
Yazmin
On May 9, 3:57 pm, Chad Etzel wrote:
> When you post a new status update, the return value/information should
> contain the new id of the update.
> -Chad
>
When you post a new status update, the return value/information should
contain the new id of the update.
-Chad
On Sat, May 9, 2009 at 3:53 PM, Yazmin wrote:
>
> Hi,
>
> I want to make sure I'm going about this the right way, so any help
> would be appreciated.
>
> I'm writing an application that
14 matches
Mail list logo