Anyone using PHP can use https://github.com/abraham/twitteroauth .
It supports the oauth_verifier (as of its most recent update).
Earlier versions of twitteroauth didn't support it and had a different
parameter order for making requests, so if you're updating, be sure to
check those things out.
Any update on this? I'm getting it on a site for certain users/
browsers even though it's all configured correctly as well.
The alerts are very intrusive for a production website when things are
configured correctly. Especially with user emails rolling in
complaining about getting the error.
When creating or editing an app through the new dev.twitter.com site,
the application will lose (or never be permitted) write access and
will only have read access.
The options to choose between read access or read write access
that's on the old oAuth page are no longer accessible on the new dev
Figured it out, the documentation must need to be updated a bit still.
Change:
twttr.anywhere(anywhereApiKey, 1.0.0, onAnywhereLoad);
To:
twttr.anywhere(onAnywhereLoad);
And it should work for you.
On Apr 15, 2:47 pm, jgervin jger...@gmail.com wrote:
I am trying to follow your example on
The same thing is happening for me. Firebug shows it as returning a
403: Forbidden.
My response text is -
?xml version=1.0 encoding=UTF-8?
ErrorCodeAccessDenied/CodeMessageAccess Denied/
MessageRequestIdD383456151C16F65/
RequestIdHostIdF7MvMBRIBSKfj5NFUl1B4nPeKW8csb98Ow0zp6oLJ/SYeaZKlqh
throwing a fail whale. You won't be able to restore your r/w setting.
[1]http://twitter.com/oauth_clients/details/
On Apr 15, 5:12 pm, Mike Davis (mcdavis) mcda...@gmail.com wrote:
When creating or editing an app through the new dev.twitter.com site,
the application will lose (or never
