Well, it’s a day for updates. Today was (at one point) the deadline for Twitter to permanently disable Basic authentication. The date has now been extended to August 31st, but the difference isn’t really significant.
The one benefit which it will provide is a little extra time to debug the new OAuth version of WP to Twitter before it becomes the only working version.
There are a lot of complications surrounding the OAuth update — most of them unfortunate. For the first time since I began work on this plugin, I had to remove features. As far as I can tell, there’s no way to operate two separate user accounts with an OAuth authenticated application, for example. As a result, I’ve had to remove the ability to assign separate author accounts for Twitter posting. As development progresses, a way forward may show up — but for now, I just don’t really have another option.
My biggest request at this time: if you can, please decide you’re willing to use this version now, to provide me with feedback so it will work as well as it possibly can when all past versions cease to be functional.
There will be problems; I’m sure of it. I just hope to find them all soon enough.
@Jeremy I have the same issue as Duerrbi, and don’t have a page that looks like the one in your screen grab.
Question here, what URL am I supposed to be using? I’ve tried my Twitter and my blog address and it says it’s invalid. Any thoughts?
I am getting the error:” OAuth Authentication Failed. Check your credentials and verify that Twitter is running.”
I have checked and double checked the tokens. They look correct. Is there any log where I could see what the more specific problem is?
hi,
i tried creating an application for twitter tools, if it works the same way in your plugin also the sorry news is twitter is blocking most of the new applications created after a couple of days.
i can’t activate the “curl_init” on my Webspace. Is that the only way how this plugin works? I would like to use it. But my provider allows me to not have this function.
Is not working on mine!
Fatal error: Class ‘OAuthSignatureMethod_HMAC_SHA1’ not found!
@Duerrbi After finding your Consumer Key and Consumer Secret, click on the “My Access Token” link on the right side menu. Here’s a picture pointing it out: http://bit.ly/9MeNlK
Hey Joe: I’m getting the same error that one of the Davids described: “Fatal error: Class ‘OAuthSignatureMethod_HMAC_SHA1’ not found in /home/server/public_html/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 61”. I’m using a shared hosting server. How might I go about describing the problem to my host?
I’ve just updated to beta 4, configured everything, and when I hit on “check support”, the output is:
“This plugin may not fully work in your server environment. The plugin failed to contact both a URL shortener API and the Twitter service API.”
Everything was working fine before, my site runs on Apache, PHP version 5.2.12.
Dude, I found the problem.
I use “Twit Connect” and probably it makes conflict with Wp-To-Twitter because both are using oauth.
I can’t find anything like an an access token string on my twitter’s application site
Thank you!! Fixed
In case everyone was wondering, Application Name: WP-to-
Hi, Joe.
I installed WordPress 3.0.1 and the host I’m using has PHP 5.2.10
Hey there,
I just installed Version 2.2.0 (beta 4) (Word Press 3.0.1), and am still getting the blank page (with header and sidebar visible) when I attempt to connect to Twitter. I’ve tried testing the “Check Support” button, but I’m informed that I have not connected to Twitter.
I went to the Twitter developer page and tried getting a new consumer key, but that didn’t help.
Thanks Joe for all of your rapid support on this issue.
Sorry, you can delete my comment. It was a prob with another plugin I updated at the same time. In this way, I think the beta4 works fine and publishs the tweets correctly, too.
One more Problem: White Screen with the activated wp->twitter beta3 or beta4 plugin after publish or update a post. But all changes are saved in the database, post is published, etc. …
I use WP 3.0.1 - all works fine since updating wp->twitter
@Alf Thanks for that information - knowing that the problem is with the templates in specific, rather than with the tag replacement is an extremely valuable piece of information.
@Miki If you need it to be functioning, feel free to downgrade to 2.1.3 and wait for more bugs to be worked out in this version.
@Crystal It looks like you need to upgrade to PHP 5. Your hosting service should have a mechanism to enable this, or you can contact their support services.
@Bryan I’m not sure why that contributor’s post wouldn’t have posted, but I’ll look into that.
Follow-Up: Updates work fine too, if I manually fill in the twitter message field or use the approbiate tags in there. If I trust on the config ( Edit: #title# - #post# #url# ) only the hashtags are shown.
For new Blogposts everthing works fine. But for Updates, the Tweets only contain the hashtags. No Post-Title, Abstract or Post-Url as configured. That worked fine in previous versions.
Having the same problem as Markus. Updated, use correct keys, everything. Nothing posts to Twitter! Any suggestions? I’ve tried all I know how to do. Was working fine until all these updates.
@Joe Dolson no worries about the support
glad you made this plugin, its very useful.
Joe,
I updated to the beta 3 release (from beta 1) a little while ago. It published to Twitter as expected. However, I still have one thing I need to check on. Prior to updating, there was a contributor’s post pending publish. I published that post after updating, however it was not posted to Twitter. It may simply be because it was there prior to updating the plugin. Will have to see what happens the next time we publish a contributors post.
Thanks for your wonderful plugin. We are using it on both AppleRelated.com and TalkAndroid.com.
Bryan
Apparently what I thought was a posting error with the test message wasn’t. I followed Joe’s set-up instructions, updated to the latest beta, and the tweet went through immediately after publishing a blog post, and it had the correct bit.ly link in the tweet.
Thanks again Joe.
John
oh i’m on the latest WP version.
I followed the instructions and get this error in WP:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /home/aphon0/public_html/my-makeup/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 18
Hello Joe,
I use the current Beta 3 version and have entered the correct Twitter Keys. Unfortunately still no posts will be transferred to Twitter. Do you have an idea?
Thank you!
Markus
@Michael Well, that proves that the connection is active and functioning — it’s just the cycle that handles posting which isn’t working. Let me think about it a bit…
Joe,
I found it and changed the blank to “yes” tried another update, no go.
I checked my Twitter page, and found this:
Tweet
Latest: This is a test of WP to Twitter. (6096968) 37 minutes agoLatest: This is a test of WP to Twitter. (6096968) 37 minutes ago from @yurself
Maybe we are making some progress?
Thanks,
Michael
@Michael It’s a custom field for your posts; it should be viewable in the custom fields area below the main post field on the admin pages to create a new post or edit your posts. It is not part of the WP to Twitter set up. If it’s not found at all on your posting or editing pages, that’s also fine - it’s programmatically equivalent to having a blank value.
Joe
Thanks for the quick response. In my basic settings, advanced settings or post page for WP there is no such animal as “jd_tweet_this” In my basic settings I have all the options checked. In the advanced settings I only have “update Twitter when a post is published using Quickpress” 2 blogs now updated with Oauth consumer and access tokens no updates to Twitter published.
I have seen the “jd_tweet_this in previous iterations of WP->Twitter but now I do not. Where would I be looking for this property?
Thanks,
Michael
It’s now working. The existing set up DIDN’T like being edited. I had to delete the application in dev.twitter and then start again.
It then worked!
@kev Must be set to read and write. I’m fairly certain that this is in the setup instructions with the plug-in; if it’s not, I must have somehow overwritten that at some point. (You can’t post to Twitter if you only have reading permissions!)
Joe should dev.twitter be set to read and write or just read?
@kev It’s worth a try. Check them carefully! Be sure to check for any extra spaces before or after (I should be trimming white space off; but I’m not sure that I actually am in that version.)
Should I try disconnecting and reconnecting to twitter in the settings?
@kev No, unfortunately. I’ll keep exploring independently.
@Michael No, that’s not what should be happening. Have you verified that your settings match your expectation? In order for an edited post to be posted, the following conditions need to be met: 1) The basic option to post edits must be checked 2) The value of the custom field ‘jd_tweet_this’ must either be ‘yes’ or blank. If you can verify that for me, it would be appreciated.
@Jorgicio That’s a new one. My guess is that your installation is including a different version of OAuth or TwitterOAuth which doesn’t include that method, but that really doesn’t make any sense, given that the get method is rather key to any use of OAuth. What versions of PHP/WP are you running?
It’s working thank you!
Any idea Joe from the export I sent you?
So I followed the update procedure. (By the way in your instructions the “application name website” would have been helpful) I then tested it with three different posts which have been previously posted. None of them showed up on twitter! Does this mean there is only one tweet per post and never an update to a post? If so there is no point for using this.
Thanks,
Michael
Hi.
I upgraded the version of Wp-To-Twitter with OAuth Support. I created the Twitter Application and when I configure, I got this error:
Fatal error: Call to undefined method TwitterOAuth::get() in /home/a1986870/public_html/wp-content/plugins/wp-to-twitter/wp-to-twitter-oauth.php on line 55
Thanks.
Found it.
I am being really thick now - where is the export option?
I don’t doubt it is something stupid Joe, but yeah I’d appreciated you looking at it. I’ll send it shortly.
@Alf Thanks - glad to hear it.
@kev I don’t know. With Beta 3 everything should generally work, although I can’t eliminate every possibility. Can you send me your plug-in’s settings export? That may help me debug your issue. The fact that the plug-in worked before has no bearing; there are no common elements between the previous authentication methods and OAuth.
Since Beta3 everthing is fine again, thanks a lot!
I had the same probs as James and kev: no tweets and the “contact both a URL shortener API and the Twitter service API.”-Error. Now the tweets came all at once.
Ok thank makes sense Joe, so why am I getting that error. This plug in worked perfectly before.
@kev The OAuth process is the entirety of your authentication with Twitter. Once you’ve added the four keys required in the OAuth setup, you’re done. Your username and password are not required. OAuth is a data exchange format which is used in place of your login and password to access Twitter.
@Beregond Thanks for noting this.
When using cli.gs I get an error message that my URL was not shortened. A bit.ly URL appears that goes to my 404 page. This happens both with and without a cli.gs API key.
No it is blank. There used to be a username and password for my twitter account, but I can’t find that now.
This is what I am trying to understand mate, am I in effect using WP-Twiiter to log onto AOuth and that then forwards the details to my twitter account?
If so do I put the AOuth log on details in:
Add Twitter-compatible Service
URI for Twitter-compatible Post Status API
Service Name
Status Update Character Limit
Post status updates to both Twitter and this service.
Your service username:
Your service password: