[twitter-dev] Read only @anywhere application bug fix

[Todd Kloots]

There is a known bug in the @anywhere application creation flow that
results in @anywhere applications having read-only access. This
results in @anywhere widgets like the TweetBox and Follow Button not
working.

We just rolled out a fix to all currently registered @anywhere
applications. However, those creating new applications over the
weekend will need to grant their application(s) write permissions by
following these steps:

1) Go to: http://twitter.com/oauth
2) Click on your application
3) On the "Application Details" page click the "Edit Application
Settings" button
4) On the settings page for your application, scroll down to the item
labeled "Default Access type"
5) Change the "Default Access type" to "Read & Write"

We apologize for the inconvenience and will be deploying a fix for
this early next week. We'll be sure to notify you all when the fix is
rolled out.

- The @anywhere Team


--
Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

[Albert Stein]

Is this what caused the issue I wrote about this morning - where the
follow buttons became "user not found" buttons after a few refreshes
and then after say 20-30 minutes the buttons would revert to the
correct follow buttons?

thanks

[Dustin Diaz]

Albert,
No. This issue addresses the fact that "write" operations were not
allowed. Thus for example, clicking following would throw a "401 -
permission denied" — However other "read" widgets, such as hovercards,
would continue to work until you attempt to follow.

[@keeev]

> following these steps:
>
> 1) Go to:http://twitter.com/oauth
> 2) Click on your application
> 3) On the "Application Details" page click the "Edit Application
> Settings" button
> 4) On the settings page for your application, scroll down to the item
> labeled "Default Access type"
> 5) Change the "Default Access type" to "Read & Write"

I can't find a label which is named „Default Access type“ please see
my
screenshot: http://cl.ly/T1C

Thanks so far! :)

[Andy]

> 5) Change the "Default Access type" to "Read & Write"

this will not work for me - no tweets will be send out so far

thanks for any hint

[maskin]

> I can't find a label which is named „Default Access type“ please see
> my
> screenshot:http://cl.ly/T1C

Please go to :
http://twitter.com/oauth_clients

//@maskin

[@iStylesMK]

> 5) Change the "Default Access type" to "Read & Write"

It's not working for us either despite the change to R/W. App key
4hIZQHIItgc3IrCKyqsjQ and testing on http://www.istyles.com/index_test.php

The follow button and tweet box loads fine but the actions do not (eg,
does not follow, does not tweet). Upon clicking follow, a popup of
https://oauth.twitter.com/2/authorize?oauth_callback_url=http%3A%2F%2Fwww.istyles.com%2Findex_test.php&oauth_mode=flow_web_client&oauth_client_identifier=4hIZQHIItgc3IrCKyqsjQ
will appear but clicking on "Connect" does nothing more than making
the popup go away (and it comes back again in a few seconds).

When the follow button is first pressed (when the popup is popping
up), the main page encounters a javascript error:

Message: 'P' is null or not an object
Line: 1
Char: 1421
Code: 0
URI: http://platform0.twitter.com/1/javascripts/follow.js

[Abraham Williams]

I just followed @iStylesdotcom no problem through your test page.

Follow my troubleshooting info: http://groups.google.com/group/twitter-development-talk/msg/080bdd99661b9b43

If it still does not work let us know your browser specifics.

Abraham

--
Abraham Williams | Developer for hire | http://abrah.am
PoseurTech Labs | Projects | http://labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.

[@iStylesMK]

Thanks, I just tested it with @iStylesMK and it worked!

I was previously testing with an account with protected tweets and
that did not work. I ran another test just to be sure and protected
accounts (or at least, my protected account) did not work but a public
account (eg @iStylesMK) worked fine.

Regards,
Ming Keong

On Apr 19, 1:49 am, Abraham Williams <4bra...@gmail.com> wrote:
> I just followed @iStylesdotcom no problem through your test page.
>

> Follow my troubleshooting info:http://groups.google.com/group/twitter-development-talk/msg/080bdd996...

>
> If it still does not work let us know your browser specifics.
>
> Abraham
>
>
>
> On Sun, Apr 18, 2010 at 18:40, @iStylesMK <m...@istyles.com> wrote:
> > > 5) Change the "Default Access type" to "Read & Write"
>
> > It's not working for us either despite the change to R/W. App key

> > 4hIZQHIItgc3IrCKyqsjQ and testing onhttp://www.istyles.com/index_test.php

>
> > The follow button and tweet box loads fine but the actions do not (eg,
> > does not follow, does not tweet). Upon clicking follow, a popup of
>

> >https://oauth.twitter.com/2/authorize?oauth_callback_url=http%3A%2F%2...