I have a web application to allow clients to update information for their
recordings (music) which are then listed on another site. I'd like to
include an area to allow them to update their Twitter status. Given that
each client already signs in to the current application, and (some of) their
T
Yes, this will be good. Are the user's oAuth token and oAuth token secret
retrieved from these lines in index.php?:
/* Get user access tokens out of the session. */
$access_token = $_SESSION['access_token'];
$access_token['oauth_token'];
$access_token['oauth_token_secret'];
Thanks for your reply
You are correct of course. I set it up that way because the only functioning
library I found for updating a user's Twitter status required them. The
other libraries seem to be using basic authentication which caused them to
fail. I'm finding oAuth challenging to use as well.
Thanks
--
Twitter
; Abraham Williams | Hacker Advocate | abrah.am
> @abraham <https://twitter.com/abraham> | github.com/abraham |
> blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>
>
>
> On Wed, Feb 2, 2011 at 07:15, Archia wrote:
>
>> Yes, this will be good.
The reason my insert code was not inserting the client tokens in my database
after returning from Twitter and allowing access to my application was that
clearsessions.php was, of all things, clearing the session variables! I use
a session variable to identify my client when they log into my site
Hi,
twitteroauth is working under domain A, but is it necessary to reproduce all
of the code under domain B to get it to work there. I've not been able to
get things working beyond step 3 of the Flow Overview under domain B. I
always end up back on connect.php under domain A.
--
Twitter devel
Why are you sending users to clearsessions.php if you don't wan't the
session data cleared? clearsessions.php is essentially a reset to simulate
logging out of an application.
The library sends users to clearsessions.php out of the box, I was asking if
not clearing the session data would caus
OK, I'll do so, but something I've done may be causing the following to be
displayed after authorizing access:
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this
address in a way that will never complete.
* This problem can some
I think I found the trouble. I had switched the order of the lines below,
putting config.php first:
require_once('/home/soundser/public_html/includes/twitteroauth/twitteroauth.php');
require_once('/home/soundser/public_html/includes/config.php');
Putting it back fixed the redirect.
--
Twitter
