Hey all,
Notice that John changed the Tumblr API header to point over to
developers.tumblr.com, he's posted another update, indicating many issues
we're raising are fixed:
http://developers.tumblr.com/post/32002964216/changelog-for-09-21-12
I'm not going to post this kind of post again, I just wanted to make sure
other developers know where to be watching for updates.
- Jason
Post Content from the update:
ChangeLog for 09/21/12<http://developers.tumblr.com/post/32002964216/changelog-for-09-21-12>
Many of you have been dismayed that you could not override the callback url
when a user was attempting to authorize their application. Good news: we’ve
patched the bug that was causing this particular issue.
Now, you can pass a url with the oauth_callback parameter and we will
redirect the user to that endpoint once you’re done.
Let’s go over a quick example.
When the user is presented with the screen to authorize your app, you
should be able to override your default callback with the oauth_callback parameter
in your url.
http://www.tumblr.com/oauth/authorize?oauth_token=your_token&oauth_ca...
The above url will redirect the user to mysite.com/oauth_callback/testing and
let you know if the user has approved or denied your app.
Some more minor fixes:
- The callback parameter is now allowed when making JSONP requests.
- Fixed a bug where the limit parameter was not being respected in the
tagged route.
- The /user/queue path now respects limit. You can request up to 50
posts at one time, and the default is set to 20.
- Fixed a bug where post fields were being reset when you edited the
post, forcing you to resend the entire post content again. Edits will now
only update the field that has changed.
- Updated the docs to reflect that /user/info should be a GET request
Please check out the latest documentation <http://www.tumblr.com/api> for
any further details. If you have any questions or concerns, ourAsk box<http://developers.tumblr.com/ask> is
always open.
