Trouble getting Twitter working

Eric,

“However, Bebop does not work with Twitter the way I thought it would. I expected users to be able to enter their Twitter handle and have their tweets come into their or the sites Activity Stream.”

That is exactly how it works. Each user has to authorise with twitter, like you just did, to get their contents on their buddypress activity stream.

Also, don’t forget that users will need to verify their tweets in the content manager if you have “should users verify imported content” = yes in the admin backend.

You can change this No, and it will pick up tweets whenever the cron is ran, no verification required.

Dale

Eric,

apologies, didn’t see your first response.

Correct, we are not going to write to twitter, but the app needs full access to the twitter API’s.

Callback url can be left blank, but for security purposes, i suggest you change it to your domain name (don’t forget the https://).

Dale

Dale, you wrote:

Okay, I see, each user enters their Twitter credentials on the Twitter site, not the WP/BP site…

I’ll write up some documentation for the github site.

Thanks!

[ Signature moderated. ]

Hi Eric,

Correct, we do not want to handle any passwords, so pass it off to Twitter to deal with. Once the user has accepted on twitter, we can start importing their tweets ??

Documentation wise that would be ace.

Thank you,

Dale

I’m getting the same problem “Failed to validate oauth signature and token”. I’ve followed all the above. I also didn’t have my Twitter app access set to read/write and I didn’t have a callback parameter. I’ve now changed this but I’m still getting the same error. Any ideas? I haven’t been able to find any documentation regarding the APIs needed for Beebop

Hi Scoobydoobydoo,

The setup documentation for each extension is something I have been meaning to do but haven;t got round to doing yet.

If you are getting the “Failed to validate oauth signature and token” message and you are absolutely sure the read/write access and callback parameters are now correct, you have a couple of options. Essentially there is ‘bad’ access tokens that are now saved in the database which need to be removed.

1. – check the ‘wp_bp_bebop_user_meta’ table for your twitter oauth tokens & secrets. Delete them and try again. they will look like so (from memory):

bebop_twitter_<your-username>_oauth_token
bebop_twitter_<your-username>_oauth_secret
bebop_twitter_<your-username>_oauth_token_temp
bebop_twitter_<your-username>_oauth_secret_temp

2. – You could also sort the ‘wp_bp_bebop_user_meta’ by extension and then delete any data relating to twitter.

3. – deactivate and uninstall bebop, then reinstall and reactivate. This will delete and then recreate the database tables. It will however remove all other data too.

Let me know how you get on.

Dale

Hi Dale

Thanks for your help. I had already cleared those tables but I tried it again and still no change. Still getting “Failed to validate oauth signature and token”. I deactivated Bebop and deleted it, logged out, cleared cache, logged back in again and reinstalled and re-set the parameters. Still getting “Failed to validate oauth signature and token”

I have a feeling the Twitter API settings are not correct because so far it’s been more guess work than anything. It’s worth noting that underneath the “Failed to validate oauth signature and token” is a button called “start authorisation”. When I click this I get sent to https://api.twitter.com/oauth/authorize?oauth_token= and I see an error “There is no request token for this page”. This indicates the Twitter parameters that I’ve set in WP are not being picked up.

It’s also interesting to note that in the table bp_bebop_user_meta the rows bebop_twitter_oauth_token_temp and bebop_twitter_oauth_token_secret_temp have no values i.e. the meta_value is empty for both. The corresponding values in the bp_bebop_options table DO have values, it’s just the TEMP parameters that are empty. Surely that’s not right?

Hi scoobydoobydoo,

The wp_bp_bebop_options table stores data such as what is found in option settings. The twitter API key and API secret are stores in that table.

The wp_bp_bebop_user_meta table stores any data that is related to users, such as usernames, access tokens, etc.

If the ‘temp’ token/secret are not being produced then there must still be issues with your twitter app api key/secret.

Can you please check your are using the correct keys – as per this image. You need to be using the ‘consumer key’ and ‘consumer secret’ that twitter provides.

Thanks,

Dale

Hi Dale

Thanks that information helped. I was using the access token details because the Bebop field label is “Twitter API Token”. It might help if you rename it to “Twitter Consumer Key” instead?

Do you have a demo or some screenshots of what this looks like when it’s all enabled? I don’t even know if it’s going to do what I want it to do so before I move on to trying the Facebook API (which looks a bit of a nightmare), it would be great to see what the end result looks like first ??

Thanks!

Hi scoobydoobydoo,

If I did that it wouldn’t be consistent over all extensions. Its a pain that they all give the same thing a different name! What I really need to do is sort out the setup guides. Its just time i am struggling with, working 70 hour weeks currently.

There are some demo screenshots over in out github documentation.
The user documentation shows you what this does. For Twitter, it basically just grabs the tweet history, and adds each tweet to the BuddyPress activity feed.

The Facebook apps are probably on the same level of complexity as the twitter apps. Nevertheless don;t be afraid – I am here if you need me!

Dale