Trying to track this bug down. Will update the thread when we've figured it
out or otherwise.
Developer Advocate, Twitter
On Fri, Apr 23, 2010 at 7:06 AM, Berto <mstbe...@gmail.com> wrote:
> Did you acquire a new token before trying to post again? I'm not
> positive, but if you didn't, it may be that the old token only had
> read permissions and didn't get updated to read/write when you changed
> your settings.
> On Apr 23, 7:17 am, Jeremy <jehe...@gmail.com> wrote:
> > Hi all!
> > I am having an issue with one of my apps. I set it up correctly I
> > think, when I do tests through the API console onhttp://
> > it posts just fine, and my app has read/write access level.
> > However on my site, whenever I try to post a new tweet, the tweet
> > process seems to go without any error messages, but nothing gets
> > posted on my twitter account.
> > I have checked it with Firebug, there is in fact an error, I get a 401
> > Unauthorised status forhttps://api.twitter.com/1/statuses/update.json.
> > It says "Read-only application cannot POST".
> > I consequently changed my app settings, and indeed it was read only at
> > first, but even after changing it to read/write, the problem remains.
> > Any idea where it could come from? What can I do to solve the issue?
> > Thank you!
> > --
> > Subscription settings: