Yes, Twitter requires a callback URL. Make a test page to display (or
save to file) your oAuth tokens. Embed those tokens into your local
test page (and remove that helpful test page on hosted server).
Develop locally, and add if-then blocks, depending if you are local or
remote. That way, you can develop locally, and upload same file, as
it will work for the remote as well. When remote, instead of "saved"
tokens, use the "live" tokens from the handshake process.
On Fri, Apr 23, 2010 at 7:13 AM, kaps <kap...@yahoo.com> wrote:
> How do you folks test your Twitter apps before uploading them to your
> hosting servers?
> Doesn't the Twitter callback URL have to be a valid website? How can
> we test locally?
> Subscription settings: