This is how I knew that the post worked: I went to the account and the
post was there. I deleted it, and tried again, and the post was there
as well, and the same happened every time I deleted and re-tested.
The error message is courtesy of the oAuth class lib, and I'm passing
it as is. I posted
What does $connection-http_code return after calling $connection-post when
you get the duplicate error message?
Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
@abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first
I am getting this:
[request] = /1/statuses/update.json
[error] = Status is a duplicate.
On Nov 30, 12:09 am, Abraham Williams 4bra...@gmail.com wrote:
What does $connection-http_code return after calling $connection-post when
you get the duplicate error message?
Abraham
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
I am getting this:
[request] = /1/statuses/update.json
[error] =
I am not doing any duplicates. I tested the app on a brand new Twitter
account, and did only a single status update. The update was actually
done, but I am still receiving the error message. I implemented
temporary fix (ignore the error code), but that's an ugly solution.
On Nov 30, 5:26 pm, Bess
Hi,
So the 403 duplicate status means the message you are sending is the same as
the last message in the users timeline.
When you say the post is posting correctly, how are you validating that this
has happened?
Also, can you show an example request that you are making, for example:
I double-checked my code, and I'm only calling statuses/update once:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .=
