Current version: 2.2.0 (beta)
Donations to date: $879.00. Downloads to date: ~258,000. Donation per download: approximately one third cent.
Comments concerning the OAuth beta
Obviously, answering every question individually is beyond what I can keep up with at the moment. Here are some general notes:
- Error: Call to undefined function curl_init()
- Yes, you need cURL support for this plugin to work at this time. This will not be altered soon.
- Fatal error: Class ‘OAuthSignatureMethod_HMAC_SHA1’
-
This comes from installations which are using a different OAuth class from that required by the plugin. Inform your host that you need to be using an OAuth class which supports that option; either by disabling their default OAuth library or by updating it to a different version.
- Parse error: syntax error, unexpected T_STRING, exp. T_OLD_FUNCTION or T_FUNCTIONor T_VAR or ’}’
-
This error comes from PHP 4 not recognizing the public or private directives in the Twitter OAuth class. You need to upgrade to PHP 5.
- Twitter is blocking your application
-
I’m sorry about that, but there’s absolutely nothing I can do about it. This is one of the powers which Twitter wanted to gain from this change: they can shut down any individual application. If they decided they didn’t like yours, that’s something I am unable to help with.
- Don’t know what URL, Application Name, or Description you should be using.
- Be aware that in general you should be referring to your own web site as the operating application. What you are essentially doing is registering your web site as a Twitter application.
- Upgrade to PHP 5
- If you need to change your hosting server to PHP 5 you need to contact your host. I can’t help you with that.
- Blank page
- I believe that this is the same as the other undefined function or various fatal errors, but on installations with error reporting disabled. If somebody can tell me otherwise, that would be great.
- Failure to post.
-
First steps: check your settings and verify everything is set up as expected. If using individual author options, disable it. Second: verify that Twitter has not disabled your application. Third: try various options, including posting an edit, posting a new post, and the test cycle before contact me. Give me as much detail as you can before reporting an error. I will no longer respond to uninformative requests for help – I don’t have the time to ask everybody for the details of their issues.
Before contacting me to make a request, please take a look at these tips on configuring and working with WP to Twitter.
Please Note: support is only provided for the most recent version of the plugin. If you are using an older version, please upgrade before requesting support.
- Do I have to have a Twitter.com account to use this plugin?
- Yes, you need an account to use this plugin.
- Do I have to have a Cli.gs account to use this plugin?
- No, the Cli.gs account is entirely optional. Without a Cli.gs API, a “public” Clig will be generated. The redirect will work just fine, but you won’t be able to access statistics on your Clig.
- Do I need a Bit.ly account?
- Only if you want to use Bit.ly URLs. The Bit.ly API doesn’t allow anonymous link shortening.
- Twitter goes down a lot. What happens if it’s not available?
- If Twitter isn’t available, you’ll get a message telling you that there’s been an error with your Twitter status update. The Tweet you were going to send will be saved in your post meta fields, so you can grab it and post it manually if you wish.
- What if Cli.gs or Bit.ly isn’t available when I make my post?
- If Cli.gs or Bit.ly isn’t available, your tweet will be sent using it’s normal post permalink. You’ll also get an error message letting you know that there was a problem contacting the link shortening service.
- Every time I edit a post, the revisions are Tweeted! Can I stop this?
- Yes. Uncheck the setting “Update Twitter when an old post has been edited” to disable tweeting of post edits.
- I just installed WP to Twitter, and my scheduled posts aren’t being sent to Twitter. What’s up?
- If these are posts you created and scheduled before installing WP to Twitter, then those posts are not going to be posted as status updates. Usually, if you edit the post or alter the schedule date, that will let WP to Twitter know that this post needs to be Tweeted.
- I can’t see the options page at all! WP to Twitter won’t work until I set my password – what can I do?
- I can’t see the settings page!
- There’s an unresolved bug which effects some servers which causes the WP-to-Twitter settings page to fail. You can get around this problem by commenting out lines
145 - 190inwp-to-twitter/wp-to-twitter-manager.php. (Version 1.3.2.); lines191-256in version 1.4.0. This bug should be resolved in versions 1.4.5 and above; please let me know if you encounter it! - I’m receiving this error: “
PHP Fatal error: Cannot use object of type stdClass as array“ - WordPress 2.9 introduced support for JSON_encoding for servers still running PHP 4. Since their implementation of this isn’t exactly the same as what I was using to do the same thing, it doesn’t work quite the same way. Some servers deal with the difference just fine; others have some trouble. I can fix this, and might still do it if I get around to it, but realistically you should be running PHP 5 or above. PHP 4 is no longer receiving security updates, and may no longer be supported in forthcoming versions of WordPress. You might as well switch now.
WordPress 3.0
upgrade from last non-beta version to Version 2.2.0 (beta 7)
If I test the Version 2.2.0 (beta 7) plugin using the check support button within the admin settings page:
if I have ‘Use a dynamic identifier with Google Analytics and WP-to-Twitter’ set, and use page title, the check support button gives a url that gives a 404 response
If I don’t have either of the google analytics options set, the check support button gives a url that works
However, in both cases the cli.gs url posted on twitter just gives a 404, rendering the plugin useless.
(I haven’t set up a personal cli.gs account)
Currently disabled on the site since it doesn’t give a usable tweet
When I test wp -> Twitter it works so the Oauth must be working. But the automatic update on posting fails.
my prob is solved! It isn’t working on only a single blog! As, I own a small blog empire and it works on the rest, so I thinks its 9/10! Thanks!
My updates are not happening either. All previous versions worked until Twitter made us create the app, which is beyond stupid for them to do that. Anyway, since I update my blog daily, it would be great if you could fix this issue.
Hey! Thanks for the great plugin!
I’m using mu! Plugin woking fine on one of my network domains but returns error on the other! The credentials are OK but I get the error! It seems like many people are getting this error and is not being addressed!
One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
401 Unauthorized: Authentication credentials were missing or incorrect.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!
WP 3.01
Just not updating status of a new post to Twitter.
Everything seems good.
For multiple sites with one app registration:
I could add the same key/secret values on every blog. Technically I don’t think that would break anything… I’ll just give it a try…
About donations:
What do you think about adding a flattr.com button in addition to the “donate with paypal” or “donate with google”?
Hi,
Just installed Beta 7 and YOURLS is no longer working? It simply gives this message: “The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues.”
I’ve checked settings and they’re correct.
Thanks
@dominik I’m not certain; I’ll look into it.
@Ben Sheldon How annoying. I didn’t know that Twitter made that assumption. I’ll provide that change in the future.
@Daniel It’s far more likely that I’ll fork than incorporate in the same plugin, but I’ll certainly weight your preference. Thanks for voicing it.
@Joe T I don’t have any specific plans; but I’ll probably do it at some point.
Is there a way to have one installation of WP-To-Twitter for all sites in a multisite network or do I really have to register every single blog?
When enabling the setting “Authors have individual Twitter accounts” the plugin adds the @twittername to the beginning of the tweet — -this breaks some of Twitter’s functionality because Twitter assumes you are sending a message to the user, not just referencing them, and it won’t show up in other people’s feed.
Instead of attaching the @twittername to the beginning of the tweet, could you either:
1. Replace the #author# tag with the @twittername if the user has set a @twittername or
2. Add a new #twittername# shortcode for formatting?
Otherwise it’s an awesome plugin. I’m using it with the Syndicate plugin to aggregate a distributed blog network and your plugin is perfect for tweeting new posts.
@Joe: Thank you for taking it under consideration! I was using both services and actually liked the idea of having them in the same application - read: no fork
Hi Joe,
Bit.ly shortening does not work for me, although all is configured correctly. Also, the full URL is not posted when I have bit.ly set up to shorten - instead it does not post a link at all!
I use XML-RPC to publish posts. Using WordPress as a URL shortener does work.
Do you plan support for custom post types in WP > 2.9? Currently I do not see a way to integrate your plugin with custom post types. Is there code that can be added to functions.php?
@nick I can’t really tell you anything more than that error message does: either your authentication credentials are incorrect, or some or all of them are missing. If you want more detailed information, turn on OAuth debugging (in the advanced settings section.)
@Gabriel, @Daniel Thanks for your comments; I’ll take those under consideration for future changes.
What am i doing wrong when i get this error,
401 Unauthorized: Authentication credentials were missing or incorrect
@Joe (cc @Daniel):
For what it’s worth I would have loved to be able to post to both Twitter and StatusNet-based microblogging services.
I actually posted here previously (under another name, but my gravatar should be the same) about this exact issue since I couldn’t get the status message to post to both services.
@Daniel Honestly, I eliminated it for two reasons: first, because I really didn’t think it was being used; and second, because it had grown so divergent from the Twitter methods that it really was a pain to maintain both.
Question: were you using both Twitter and Identi.ca, or just the latter? I’m considering forking the plugin to create a second plugin which handles other APIs, or rewriting a few things to make the secondary posting service easier to maintain, but I haven’t really decided.
Oh NO Joe!
Why did you completely eliminated the secondary posting service feature?! I just did my usual update and the function was gone! Without a warning! And it was working fine before!
I loved your app just because of that. The possibility to post to my identi.ca account is crucial to me. Or was I really the only one using this feature?
Joe, please! Bring it back!
@Mohammad Yeah, those screenshots are pretty old; they don’t apply to the OAuth version. The plugin knows your Twitter account on the basis of your OAuth authentication keys.
@Ann I truly wish I could help you with that, but I have no control over that factor. This is an ability that Twitter has gained with the new authentication method; I don’t know what grounds they may use for deauthorizing your application.
thanks Joe,
so this plugin how know our twitter account?
in this screenshot i see that the section for enter account details , but in real this isn’t exist: http://s.wordpress.org/extend/plugins/wp-to-twitter/screenshot-3.png
@Mohammad There is nowhere in the plugin to enter that information; it’s not required.
@others The upgrade to beta 7 may fix some of your problems, but keep me updated. There was no change to the OAuth process, so those issues are not resolved; but I did significantly revise error messages, so you may be able to provide me with more detailed information.
hi,
in the WP to Twitter Options page , i can’t find a section for enter Twitter username and password.
MY oAUTH TOKEN WAS JUST SUSPENDED BY TWITTER FOR VIOLATING THE TOS!!!
I followed the directions correctly and put in the required information. A few days later, I just received an email claiming that the token was suspended because my application violated the TOS. They did not tell me HOW it violated the TOS, but needless to say, I’m quite upset over the matter. I don’t even know what I did wrong or how to fix it.
Has anyone else run into this problem?
Current WP Version: 3.0.1 upgraded from 3.0
After filling out the Twitter Dev for the new OAuth I get the following error when attempting to hit the check support button at the bottom of the plugin page. I filled out the dev app form as per your instructions, pasted in all the correct keys and secrets. I checked with my host (inmotion hosting) I have PHP 5.2.6 installed
“WP to Twitter failed to submit an update to Twitter.”
Vicki/Adrian: I’ve found that since the Beta 6 is posting blank tweets (except for tags) when editing and updating a post, I’ve have to check the “Don’t Tweet This Post” when doing any edits, to keep the erroneous tweet from going out.
Joe: It’s not a real update tweet, as the “Updated” prefix is not being used and the post text is non-existent. It’s just posting the hashtags.
All: I don’t know what twitter thinks of sending multiple blank tweets to Twitter and may be the reason for your accounts being
Joe,
Having a config problem.
WP3.01 Apache & Beta 6 Fresh install
Once I have entered my OAUTH stuff I click on the CONNECT TO TWITTER button and all I get is a clear screen with the question - “Are you sure you want to do this?” and nothing else.
Thoughts?
Hey Joe, just wanted to follow up with you and let you know I am still having an issue with B6 that I noted with the earlier betas.
On a couple of sites, we have “Contributors” that will write a post, who then submit it for review. If the editor is good with the post, they will publish it. For some reason, these posts are not being posted to Twitter.
Other posts, including saved drafts that are published later, appear to post to Twitter with no issue.
This is the second time i send a bugfix
There is a bug when you’ve a very collaborative blog. In this case when people are not “editor” but only “collaborators” they are not able to publish posts.
So they put it as “pending review” . Unfortunately wp-to-twiter does not manage this case so you’ve to modify the jd_twit function accordingly by copying and paste my code
Have a nice day BOIADIO
— - CODE — -
function jd_twit( $post_ID ) {
$jd_tweet_this = get_post_meta( $post_ID, ‘jd_tweet_this’, TRUE);
if ( $jd_tweet_this != “no” ) {
$jd_post_info = jd_post_info( $post_ID );
$sentence = ”;
$customTweet = stripcslashes( trim( $_POST[‘jd_twitter’] ) );
if ( ( $jd_post_info[‘postStatus’] == ‘publish’ || $_POST[‘publish’] == ‘Publish’) && ($_POST[‘prev_status’] == ‘draft’ || $_POST[‘original_post_status’] == ‘draft’ || $_POST[‘prev_status’] == ‘pending’ || $_POST[‘original_post_status’] ==’pending’ || $_POST[‘original_post_status’] == ‘auto-draft’ )) {
// publish new post
$newpost = true;
if ( get_option( ‘newpost-published-update’ ) == ‘1’ ) {
$nptext = stripcslashes( get_option( ‘newpost-published-text’ ) );
}
} else if ( (( $_POST[‘originalaction’] == “editpost” ) && ( ( $_POST[‘prev_status’] == ‘publish’ ) || ($_POST[‘original_post_status’] == ‘publish’) ) ) && $jd_post_info[‘postStatus’] == ‘publish’) {
$oldpost = true;
// if this is an old post and editing updates are enabled
if ( get_option( ‘oldpost-edited-update’) == ‘1’ ) {
$nptext = stripcslashes( get_option( ‘oldpost-edited-text’ ) );
}
}
if ($newpost || $oldpost) {
$sentence = ( $customTweet != “” ) ? $customTweet : $nptext;
if ($jd_post_info[‘shortUrl’] != ”) {
$shrink = $jd_post_info[‘shortUrl’];
} else {
$shrink = jd_shorten_link( $jd_post_info[‘postLink’], $jd_post_info[‘postTitle’], $post_ID );
store_url( $post_ID, $shrink );
}
$sentence = custom_shortcodes( $sentence, $post_ID );
$sentence = jd_truncate_tweet( $sentence, $jd_post_info[‘postTitle’], $jd_post_info[‘blogTitle’], $jd_post_info[‘postExcerpt’], $shrink, $jd_post_info[‘category’], $jd_post_info[‘postDate’], $post_ID, $jd_post_info[‘authId’] );
}
if ( $sentence != ” ) {
if ( get_option(‘limit_categories’) == ‘0’ || in_allowed_category( $jd_post_info[‘categoryIds’] ) ) {
if ( get_option(‘jd_use_both_services’) == ‘1’ ) {
$sendToTwitter = jd_doTwitterAPIPost( $sentence );
$sendToTwitter = jd_doUnknownAPIPost( $sentence, $jd_post_info[‘authId’] );
} else {
$sendToTwitter = ( get_option( ‘x_jd_api_post_status’ ) == ” )?jd_doTwitterAPIPost( $sentence ):jd_doUnknownAPIPost( $sentence, $jd_post_info[‘authId’] );
}
echo $sendToTwitter;
if ( $sendToTwitter == false ) {
update_post_meta( $post_ID,’jd_wp_twitter’,urldecode( $sentence ) );
update_option( ‘wp_twitter_failure’,’1’ );
}
}
}
}
return $post_ID;
}
— — END OF CODE — —
I am having the same problems as Nick.
“There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.”
” One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!”
I have disconnect and reconnected with twitter several times, and each time went through all the steps as instructed. It saw Twitter connected successfully until it attempt to connect with twitter.
Running WP 3.01 from a linux host.
WordPress 3.0.1. , Apache/Linux, Upgraded plugin, previous version (not sure #)
Previous versions of the plug in allowed us to add a Twitter account to a specific author. When an author posted, it showed up on the main site’s Twitter feed, plus the author’s Twitter feed.
This is the main reason I was using this plug in. As I read through these comments and through the instructions, it looks like this feature will no longer be accessible due to Twitter changes. Can you confirm? We used to have a Twitter username and password section when you looked at the user information - now gone.
If this feature is gone (I understand it’s most likely due to Twitter’s requirement to register applications) is there a suggested work-around to get this to work?
whay wp to twitter post the updated post? and he post only hashtags!
this my settings - http://img801.imageshack.us/img801/9396/basic.jpg
this is a hastags - http://img842.imageshack.us/img842/6043/advancedx.jpg - this hastags post after i update the post, posting to thitter only this to words.
Same problem as @Moritz et al.
Apache/Linux virtual server. Just upgraded from WP2.7 to 3.0, all fine.
Wanted to tweet new posts and this looked like the best plug-in.
Followed instructions to the letter, checked and re-checked all settings, fails to connect to twitter.
Then tried Twitter Tools by Crowd Favorite. Same problem.
WP latest
Linux
Upgrade
beta 5 - beta 6
I also have the Post to Facebook app on my weblog. When I click on post to facebook, after the post has been successfully published and the Twitter entry is complete, the WP to Twitter app posts to Twitter again, but only with the #hash tags, nothing else.
This isn’t a massive problem, since I can delete the secondary Twitter post at once, but I don’t want to stop using either app!
Viki.
sorry and this error i also get….
WP to Twitter failed to submit an update to Twitter.
this is the only thing that comes up for me….
There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.
Any ideas?
thanks nick
@Moritz You seem to be experiencing a problem that a few others have experienced; the plugin does not receive any response from the Twitter API. I don’t yet have an answer for you.
@Adrian Thanks for your comments. I’m taking the time with these beta versions to re-write almost the entire status update process that the plugin uses, so it’s good to find these issues now.
“Update when a post is edited” is not checked, but if i update the post, plugin send the hastags (Custom text after all Tweets) to twitter
Function “Custom text after all Tweets:” work thery strange, he post this text from this form to twitter automaticaly after 5 mintes to post the normaly post with this hashtags…
Cindy, I got the same thing because I cut and pasted the url. Make sure your callback url does not have a space before or after the url that may have been inserted by accident.
ican’t Register my site as an application on Twitter’s application registration page to install WP to twitter plugin.
the error message: the call back url is invalide format.
WP 3.0.1
Server is Unix, do not know what type.
New installation of plugin Beta 6.
Double-checked all instructions along with all suggestions in FAQ, double-checked all Twitter settings on Twitter and on plugin settings. Everything seems to be as specified in instructions.
When connecting to Twitter from WP plugin settings page, get “OAuth Authentication Failed. Check your credentials and verify that Twitter is running.” Debugging is on, have captured output, but cannot post here as it contains the keys. Don’t know what else to look at or provide, although did notice that OAuth version in debug output is 1.0 and OAuth version on Twitter is 1.0a.
Hey Joe, AWESOME plug-in. I just upgraded and completed the OuAth registration and WP to Twitter is working perfectly. (GREAT INSTRUCTIONS) Only ONE issue. I used to be able to re-tweet posts to twitter using QuickEdit in WP. I figured it out by accident and it made building a following and driving traffic a breeze. LOVED IT! Now it doesn’t work and I feel like someone took my cake and ate it too. My site is WP 3.01. Any ideas how to get the QuickEdit to repost tweets? Thanks! -John
Great, now it’s ok!
i’m happy to helped you to improve this wanderful plugin!
good work
Giorgio
@Giorgio This bug is fixed in beta 6, released just a few minutes ago.
if twitter give to your request a response when publish something on it, it can be possible print this response on wp-to-twitter settings page when there was an error?
maybe it’s very useful to understand what is the problem for the publisher.
For example today i wrote a new article, and now it was published, but when i modify it and post again, it doesn’t go on twitter again. I can’t understand why…i already set the first two settings in “base section” of wp-to-twitter settings page in WP, but nothing.
can you explain why?
thanks
@Michael Yes, it’s confusing - you need four pieces of information, and they aren’t presented to you all in one place.
@Gaz No, I don’t think that’s likely. Twitter implemented OAuth quite a long time ago; August 29th is the date when they will stop allowing Basic Authentication — there won’t be any change to OAuth at that time.
To those of you with applications that aren’t posting - can you verify for me that your Twitter application is registered 1) as a browser app, not a desktop app and 2) with read/write permissions?
Best,
Joe
Found the button to request the Access Token secret. There are 2 pages for the apps. One about the connections in the settings, one about API. The one with API you get the button to request it.
Joe
Just a thought with all these repeated error reports …. I thought the last report said Twitter would be implementing oAuth from 29 August?
Is it possible some of the posting failures are due to oAuth not having fully rolled across all Twitter servers and territories?
(I’m still sitting on the older version right now - it’s never been a high traffic generator for me, so I can afford to wait until Twitter tells me to upgrade then I know their end of it is live).
Gaz
Thanks for the great plugin! Is there any way to disable the “Twitter now requires authentication by OAuth” warning? When using the plugin on a multi-user site, some users do not use the plugin and there seems to be no way to disable the error message for some users.
Thanks!
i’m in the same situation as Melissa…all settings are ok but nothing go on twitter.
thanks for your work
bye
Giorgio
I’m using WP 3.0 and did the automatic upgrade for your plugin. Followed all the instructions on creating an app, etc. All my settings are correct, verified with my server and that came back ok too. But…nothing is posting to twitter since I did the upgrade.
I got “OAuth Authentication Failed. Check your credentials and verify that Twitter is running.” Can I run some debug or whatever to help find out whats up?
FYI, I was having the “blank page” issue and I couldn’t figure out how to check if the error messaging was off (apparently WP_DEBUG is deprecated) but it turned out that the issue was my server was defaulting to PHP 4 instead of PHP 5. Just mentioning it in case that helps others…
I registered my blog as an application, but I didn´t get an “Access token secret”, in the description you say there is a link right hand side of the app page, I don´t have that link
Hi. I’ve got the following error:
OAuth Authentication Failed. Check your credentials and verify that Twitter is running.
I’m using WordPress 3.0.1. Server: Apache. And I upgraded Wp to Twitter beta 4 to beta 5 (2.2.0)
Getting this error
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /home/content/w/i/n/winemarket/html/pocketworpress/wp-content/plugins/wp-to-twitter/jd_twitterOAuth.php on line 18
Hi Joe,
great script, very comprehensive. I have a small issue that is more compatibility with another plugin, I use WPLifestream and when using wp-to-twitter I enter into an endless loop, I tweet, lifestream picks it up, wp-to-twitter picks up the lifestream post and tweets (repeat) I’ve turned off all the posting options on the first section and it still wp-to-twitter sends a tweet, I’ve used category limiting, and it still sent it. It seems I cant even turn it off to start troubleshooting options
Wordpress 3.01
Apache Server
Upgrade
Not sure which version upgraded from
Since upgrading, everything is working fine except my cli.gs shortening. I have changed the cli.gs code to see if this helps, but it does not. The App posts the blog to twitter fine, just not ulr shortening.
@all Please read the notes at the top of this page.
I have 8 sites all working perfectly with wp-twitter until upgraded and filled in all details correctly I think to Oath. Today I have 8 emails saying I have been suspended from Twitter and I have done nothing wrong. Any help appreciated
Running the latest wordpress with wp-to-twitter updates. I’m getting this mesage:
Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /home/content/t/w/i/twintone/html/pipcast/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 18
Any idea?
Thanks
D!
Me again,
Joe, your solution has worked out for me. Its up and running again
.
Thanks,
~ Tony
Thank You Joe for the quick reply,
i will enable cURL on my Server.
I hope that’ll be the solution.
~ Tony
Thanks for your plugin, but it’s not working. I think that settings are ok, when I push the button Check Suport, no error message is displayed and a test post is sent to my twitter. But when I publish a new post, or update an old one, nothing appears in my Twitter.
I noticed that when I write a new post, the field jd_tweet_this is not populated, and if I try to do mannualy, when I publish the post, the field is blanked. the other fields used by WP-to-Twitter doesn’t appear.
If I update an older post, the field jd_tweet_this appears wiht ‘yes’ and the older fields appear too, but when I save the changes, nothing appears in Twitter and the field jd_tweet_this is blanked.
Can you help me? Thanks.
Sorry my poor English, I’m from Brazil.
Obviously, answering every question individually is beyond what I can keep up with at the moment. Here are some general notes:
1) Error: Call to undefined function curl_init()
Yes, you need cURL support for this plugin to work at this time. This will not be altered soon.
2) Fatal error: Class ‘OAuthSignatureMethod_HMAC_SHA1’
This comes from installations which are using a different OAuth class from that required by the plugin. Inform your host that you need to be using an OAuth class which supports that option; either by disabling their default OAuth library or by updating it to a different version.
3) Parse error: syntax error, unexpected T_STRING, exp. T_OLD_FUNCTION or T_FUNCTIONor T_VAR or ’}’
This error comes from PHP 4 not recognizing the public or private directives in the Twitter OAuth class. You need to upgrade to PHP 5.
4) Twitter is blocking your application
I’m sorry about that, but there’s absolutely nothing I can do about it. This is one of the powers which Twitter wanted to gain from this change: they can shut down any individual application. If they decided they didn’t like yours, that’s something I am unable to help with.
5) If in doubt about what URL, Application Name, or Description you should be using, be aware that in general you should be referring to your own web site as the operating application. What you are essentially doing is registering your web site as a Twitter application.
6) If you need to change your hosting server to PHP 5 you need to contact your host. I can’t help you with that.
7) Blank page - I believe that this is the same as the other undefined function or various fatal errors, but on installations with error reporting disabled. If somebody can tell me otherwise, that would be great.
First steps: check your settings and verify everything is set up as expected. If using individual author options, disable it. Second: verify that Twitter has not disabled your application. Third: try various options, including posting an edit, posting a new post, and the test cycle before contact me. Give me as much detail as you can before reporting an error. I will no longer respond to uninformative requests for help - I don’t have the time to ask everybody for the details of their issues.
Thank you - I’m closing comments on all WP to Twitter related posts except for the Support thread.
Added OAuth details but still get;
Twitter now requires authentication by OAuth. You will need you to update your settings in order to continue to use WP to Twitter.
Hi, I’ve added the OAuth account details and I keep getting;
Twitter now requires authentication by OAuth. You will need you to update your settings in order to continue to use WP to Twitter.
What next? :S
T
Your Plugin is great! I’m still trying out other Twitter posters, but if you could integrate the plugin: TWITTER FRIENDLY LINKS as a URL shortening option, that would put your plugin at the top!
I followed all the instructions, registered the application, added the relevant codes, and get this error message:
Fatal error: Class ‘OAuthSignatureMethod_HMAC_SHA1’ not found in /home/thodges/public_html/blog/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 61
Thanks in anticipation.
Hello Joe,
i am getting errors, when i am trying to input the new twitter settings.
Fatal error: Call to undefined function curl_init() in /var/www/big-blogger.de/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 200
I am using the latest WP version as of right now.
Apache/2.2.9 (Debian) PHP/5.2.6-1
I hope you’ll find a solution to this problem.
Thanks,
Tony
Joe,
Beta 4.
**********************************
When you say 2.2.0, which version of 2.2.0 are you referring to: beta, beta 2, or beta 3?
Having trouble with this part of your instructions. There is no “My Access Token” link on the right side of my app page… I’m stuck! Can you help me out? Thanks!
3. Copy and paste your Access Token and Access Token Secret into the fields below
On the right hand side of your application page, click on ‘My Access Token’.
WP 3.1 , Apache, upgrade, UPGRADE FROM, Previous to this one.
Blank page when doing the connect to twitter, except for “Twitter now requires authentication by OAuth. You will need you to update your settings in order to continue to use WP to Twitter.”
Hi Joe,
I’m getting the error
“Fatal error: Call to undefined function curl_init() in /mnt/web9/21/47/52361047/htdocs/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 200”
after filling out the infos required by OAuth.
I know it’s because of the missing “Client for URL” support of my Webhoster but I don’t want to pay twice as much as I do now just to get the cURL support.
Ain’t there any other solution to this problem ‘cause I rly need your plugin.
Thanks for your work.
Having the same issue as Caryn Law. Tried everything can’t seem to fix it. I get “OAuth Authentication Failed. Check your credentials and verify that Twitter is running.”
Hi Joe,
Just updated the WP to Twitter plug-in and I am getting the same message as @Caryn above. I will check back for advice on how to proceed (have checked/double-checked for leading/trailing spaces). I don’t know my server type or which version I upgraded from. I’ve been upgrading as you provide them, so hopefully it was the last version.
Thanks for all your work!
WP-Version: 3.0.1
Server-Type: Apache on Gentoo-Linux
Upgrade to beta 3 (from which version I dont know)
I have a similar problem as Viki (http://www.joedolson.com/articles/wp-to-twitter/support/comment-page-15/#comment-35519).
On postupdate a tweet goes out to twitter, but the shortcode for title and url (#title# and #url#) won’t work. I mean, there is no title and no url inside the tweet. Hashtags will work fine.
On settings-page I have “[Update] #title# #url#” in the field for updates.
A tweet looks like:
[Update] #hashtag1 #hashtag2
I like this plugin and so hope for a fast and working Update.
New Posts I haven’t tried yet.
Your active support despite Twitter making it difficult is pretty commendable, though. Nice job.
@Bruce Your frustration is fully understandable. I wish I could say that the authorization process will get easier, but in all honesty I don’t know that it would be a true statement. That’s dependent on Twitter’s decisions.
Just wanted to express my regrets at having to abandon your plugin. I tried to authorize it, but it was just too hard to do, and I know what I’m doing. It is just easier to use twitterfeed, even though they don’t offer all the very nice message content options.
Sorry - I understand you must find this very frustrating.
@Caryn Well, I’m not sure. I’ll have to think about it. I’ll look and see what error messages I can get Twitter to produce in that verification, perhaps, and see if we can learn anything about why they’re rejecting it.
I also turned off my TweetDeck application in the hopes that this was overload the API, but that still didn’t help.
(Heh, sorry for the comment spam but I figured it would be good to be thorough.)
Just as an update, I even tried deleting the app I registered in Twitter’s dev service, recreating it, reinputting my keys and tokens and being very, very careful to make sure there was no leading or trailing spaces, and I get the same error.
I checked for trailing spaces, yep. Made sure there were NO spaces that could be messing it up.
@Caryn Did you check for trailing spaces, as well?
Hi Joe,
Thanks for the super fast response. I triple-checked my consumer and token keys and secrets — there are no leading spaces, and they truly are exactly as they are on the twitter dev page. I cannot for the life of me figure out why it’s telling me the credentials are failing. Twitter is up and running, so I know it’s not that.
@Caryn Your twitter username and password are not used in OAuth authentication. I’ve updated the instructions following your comment to make this clear. The only possibilities are exactly as stated — either your authentication credentials are incorrect or Twitter was unable to accept your request. My guess is that the credentials are incorrect; one of the problems with this set up is that those credentials are so complicated that they’re practically impossible to check visually. One recommendation (and this will be gone in the next version) is to check for empty spaces before or after your credentials. Extra white space may cause Twitter to reject the information. Also, that checkbox needs to be updated — it is no longer possible for other authors to have their own Twitter accounts. They can have accounts with other services, but not with Twitter. Thanks for noting that.
hello!
I’ve gone through all of the steps to install this and made sure that all of my keys and tokens were set correctly. When I hit the “Connect to Twitter” button, though, I get this error:
OAuth Authentication Failed. Check your credentials and verify that Twitter is running.
I don’t know what credentials are wrong. I don’t see anything in the settings that allows me to actually set my Twitter username and password, yet it sounds like it’s failing on that. I saw a checkbox to allow different authors to have their own Twitter posts that they can set the info for in their profiles, but even on checking that box I see no area anywhere in WordPress where I can actually set my twitter username and password.
What am I missing?
Thanks!
WP version: 3.0.1
Server type: Apache, I think?
Installation: new
@Steven That sounds like you’re not on PHP 5. You’ll need to upgrade PHP 5 to continue using this plug-in.
@Viki Checking - you’re saying that the plug-in tweeted an update but did not include your custom information?
All was working great until I upgraded to the latest version. Now when I try to connect to Twitter (via the settings page) I get the following:
“Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in C:\Inetpub\vhosts\StevenStarr.net\httpdocs\blog\wp-content\plugins\wp-to-twitter\twitterOAuth.php on line 18”
Updated to beta 3, re-posted the article, and the post was tweeted.
I hadn’t changed any categories for at least 2 weeks [added one back then] and didn’t even think about the possibility of needing to change any settings which may explain why I didn’t notice that unserialize() issue.
Now to figure out why that other tweeting plug-in adds all the goofy code (after updating SEO Ultimate)… {Yes, posts get tweeted twice. A straight URL and a shortened URL plus some other differences/benefits.}
Thank you for the speedy (and most accurate) reply.
Latest WP
Linux
Upgrade
2.2.0 (beta 1) to 2.2.0 (beta 3)
Uploading to Twitter the # are included but New Post, Title and URL missing.
Just for information!
Viki
@Trimmer of Claws First, thanks for your comments. Second, you’ll need to upgrade to Beta 3 (released this morning) before I can effectively respond to at least one of your points — Beta 2 had a problem in actually posting to Twitter. Your other questions are duly noted; although the unserialize() issue is not actually new - I’m surprised you haven’t had it before. I’m fixing it now, though. Re: frequent upgrades. Yes, that’s not surprising. It’s difficult to support, essentially, an unknowable number of unknown systems and configurations, even with the work WordPress has put into making that easier. Since most plug-ins are one-person operations, our capacity for testing is limited.
Hello from Princeton,
Just upgraded “WP to Twitter” via FTP to 2.2.0 beta 2 this morning. [WP 3.0.1 on L{Redhat}A{1.3.41}M{4.1.22}P{5.2.3}(64 meg allocated)] For the name of the application I used WPTweets and linked it to your “WP to Twitter” page.
(That part wasn’t in the instructions)
After filling in the ‘consumer’ and ‘access’ information and ‘connecting to Twitter’, I received this error: “Warning: json_decode() expects parameter 1 to be string, object given in /home/xxx/public_html/wp-content/plugins/wp-to-twitter/wp-to-twitter-oauth.php on line 57”.
Clicked the “check support” button and “This is a test of WP to Twitter. (5678332)” was posted to Twitter as expected. Posted a new article on my blog but that was not posted to Twitter.
I see a new error on the settings page under ‘Limit Updating Categories’: “Warning: unserialize() expects parameter 1 to be string, array given in /home/xxxx/public_html/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 990”. This error appeared after checking a new category to be included and clicking Set Categories. I rechecked all the categories (except the two I don’t want tweeted) and re-saved - this time with no error.
Updated the article and still no Tweet (checked the the other settings and they seemed okay).
Although I don’t think they should affect each other Wordbooker only posted to my fan page rather than both fan and profile pages after doing this upgrade.
{Side note: I am updating plug-ins literally daily. Frequently I am finding that something [a feature] will work one day and then not the next after some upgrade. Some functions return that that or another plug-in is updated and some things remain broken.}
Lest I be rude, Thank you for your plug-in.
Doug
@Dave Also, it sounds like you’re not using Beta 3; that text is more detailed in the most recent version. You should update again as soon as you can. (It doesn’t matter whether you’ve already set up OAuth.)
@Dave Whatever you want it to be; it’s your decision. I recommend the name of your web site.
Hi, what is Access Token Secret ? is no button anywhere to get the Access Token Secret please screen
Upgraded to the beta and I’m having trouble registering using the new methods. Specifically this statement. I have no idea where to find that information - Can you point me in the right direction?
Your Application’s Name will be what shows up after “via” in your twitter stream; previously, “WP to Twitter”
@Steve Just to clarify, your custom text did post to Twitter, but the rest of your tweet text did not? The custom field jd_tweet_this has been changed; it should not be populated by default any more.
@Harm Thanks. I’ll see what I can do.
I’m getting a: “Cannot redeclare class OAuthConsumer” error when updating to 2.2.0 beta 3. In OAuth.php on line 12. Consider it a bug report.
Good work BTW!
I installed 2.2.0 beta, beta 2 and beta 3 today. I have been unable to successfully make any posts to Twitter. I know its connected because I put some custom text in front of the tweet, and the custom text showed, but the post did not. Also, I noticed the jd_tweet_this stopped auto populating with “yes”. I LOVED this plugin. I hope things start working again soon.
When you say 2.2.0, which version of 2.2.0 are you referring to: beta, beta 2, or beta 3?
Installed 2.2.0, added Twitter keys tokens and secrets and Cli.gs API key - looks like Twitter’s connected cuz the button says “Disconnect from Twitter”, but when I click “Check Support”, I get the dreaded:
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.
What am I doing wrong?
I can’t get past the registration screen — I tried to authenticate with OAuth; it fails and I get this message: ‘The application name can’t include “twitter”.’
Hi there,
i had updated the plugin for my wp and i have all my settings for twitter (username, consumer key, etc.) but nothing will be published on twitter. I use wp 3.0 and wp to twitter Version 2.2.0.
I get the following error when trying to use oauth (I enter in all the token/keys properly):
Fatal error: Call to undefined function curl_init() in /home/xxx/public_html/wp-content/plugins/wp-to-twitter/twitterOAuth.php on line 201
I am on WP 3.0.1 and just updated to 2.20.
I got the false positive on the test, but posts are appearing on Twitter OK with oauth. WordPress 3.0.1, upgrade, blt.ly.
The new WP to Twitter with oauth isn’t working. I went through all the steps, set up the API thing and it connected to it in my WP dashboard just fine… but it’s not publishing any of my posts to Twitter.
i’m running an arcade theme over at http://www.zombiegameworld.com. There’s a custom plugin for adding content to the site, but i haven’t tried that in conjunction with your plugin yet. i just went to the regular ol’ “Add Post” bit in the sidebar and threw up a test post. It did not get tweeted.
i changed the default structure of the tweet to this:
We just added #title# to our great collection of zombie games! #url#
i doubt that has anything to do with it, but i’m mentioning it just in case.
- Ryan
I don’t have edits set up to publish. I was posting as an admin account, as well as a contributor account that required an admin account to publish. I did notice it doesn’t look like the custom fields are being populated as they were before the update.
Running the latest version of WP.
@Ryan, @Bryan I’m not overly worried about the false positive error messages right now; although I’ll definitely look at that. The failure to publish is of more concern, though! Are you publishing normally (e.g., through the Posts interface) or via some other method? What version of WordPress are you using? Are edits posting to Twitter?
I’m experiencing the same issue as Ryan described. Test successfully posts to Twitter despite an error stating that it could not connect to the URL shortener (bit.ly) or Twitter. However, new posts are not published.
i figured that out moments later. Such a dumbass … i’m so sorry to have bothered you with that, Joe. (At least it was easy to answer, though
Luckily, i run the server, so i got it sorted out quite quickly.
i’m having the same problem as Nick, tho … i get the report that it can’t find my URL shortener or Twitter, but the tests work. And when i add a post, it doesn’t seem to tweet anything.
- Ryan
Never mind, I figured it out. It’s working now, but it reports back that it couldn’t reach my url shortener or twitter, even though the tests went through.
The instructions are confusing. In your instructions it says:
3. Copy and paste your Access Token and Access Token Secret into the fields below
On the right hand side of your application page, click on ‘My Access Token’.
Access Token
Access Token Secret
Twitter gives me this:
# Request token URL
http://twitter.com/oauth/request_token
# Access token URL
http://twitter.com/oauth/access_token
# Authorize URL
http://twitter.com/oauth/authorize
There is no button anywhere to get the “access token” or “access token secret” what now?
That means that your server doesn’t have cURL support, which the twitterOAuth library requires. You should contact your server admin or host and see if it can be enabled.
I’d prefer not to require cURL, but I haven’t elected to modify the twitterOAuth library yet.
HI! i was entering all of my keys and such into the Settings page, and when i was finished, i cliked the Connect to Twitter button and got this error message:
Fatal error: Call to undefined function curl_init() in C:\wamp\www\gameWorlds\zombieGameWorld.com\wp-content\plugins\wp-to-twitter\twitterOAuth.php on line 201
WordPress is version 3.0.1. i’m running version 2.2.0 (beta) of the plugin.
Any ideas?
Thanks!
- Ryan
So, I haven’t really been responding to requests for support much recently. This is because a very large portion of this requests bear on Twitter API issues; and my focus has been on getting the OAuth implementation ready. Since that means a completely different method of handling the Twitter API, there was little point in addressing other issues.
As of today, I’ve released the beta version of the OAuth implemented update of WP to Twitter; I encourage those with problems of any sort to upgrade to this version to begin providing me with feedback concerning issues with the new version. Your problems probably aren’t gone; and I may well have created new issues for you. However, OAuth is going to be the only choice soon.
WP 3.0.1, Win2003/Apache, new install. Since installing this plugin it’s worked beautifully. Then, a few days ago it just stopped and gives me this error:
There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.
and this:
One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!
This is true on TWO separate blogs I have. It started at the same time on both, and no matter what I do it doesn’t work. I’m able to go to twitter and tweet manually so access from the network is not the problem.
Greetings,
I am using WP v3.0.1 with a Linux server. This is a first time install of
WP -> Twitter. The plug-in works in the sense that it posts to Twitter, but it will not shorten my URL. I am using the bit.ly service and they tell me all is configured correctly on their end. The username and API key is correct so I am confused as to why the plug-in will not shorten the URL when posting. Any assistance or ideas as to why the URL won’t shorten would be appreciated.
Hi I’m using WP 3.0.1 and WP to Twitter version Version 2.1.3
I’m trying to get my custom post type to send to twitter like normal posts. Not sure why it’s not working… any ideas?
Thanks in advance!
WP v3.0.1, WP-to-Twitter v2.1.3
Apache/Linux
New install
Editing posts via Quick Edit cause the post to be tweeted as New (not as an Update). This happens every time I quick edit a post.
Keep up the good work, Joe.
Question about the “Individual user” group. are you going to allow a fourth option that sends tweets to the author’s twitter as well as the website’s twitter?
Version 2.2.1
Apache
Upgraded from previous version
I have only this option checked, “Update when a post is published,” but when I unlinked a broken link in an old post via Broken Link Checker plugin, the post was re-tweeted.
Please advise. Thank you.
Is there a way to change the placement of the individual authors’ Twitter username in the resulting tweets? Right now it defaults to at the beginning of the tweet meaning that unless a @CalgaryPolitics follower is also following the author, they can’t see the tweet.
What I’d prefer to do is have “New Post: #title# by *twitterusername* #url#”.
Hi - thanks for all your comments. I’ll be working on WP to Twitter in the next couple of weeks, and will try and address these issues. There is a problem with the controls to determine when to update Twitter; it seems like I can’t find a combination where I can post to Twitter following an email update but NOT post to Twitter on other edits where it’s not desired. This has been a pain, and I’m going to revamp that entire system in the next version.
@ Tony F I got the same message. Only I don’t get the error message.
* WP version: 3.0.1
* Linux Server (Debian)
* New installation
* No upgrade
* If I have edited an article, the plugin put a tweet on my page. But the shortening service isn’t working.
Hi,
I have disabled the option to send a tweet when a post is updated but today I just added new tags to an old post via Quick Edit and the plugin tweeted this too.
I think that is an error, is it not?
Thanks @Gaz
I have not started bulk submitting posts however posts are now not being tweeted. I have no idea what the reason for this is. It randomly started today.
2 PROBLEMS:
— - 1: WP to Twitter & Twitter to Facebook (page)
… When WP to Twitter tweets it will not go to my FB wall (using Smart Twitter for Pages app)
… When I tweet manually it DOES go to my FB wall
Has anyone had a similar problem? Does anyone else link to a FB page this way?
— - 2: WP to Twitter has stopped working
“Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post.”
…I do not have any problems accessing twitter, however nothing is posting. I cannot think of any changes I have made
Before Twitter to WP stopped posting I always got the “There’s been an error posting your Twitter status!…” message (however the blog post did still post).
Any thoughts as to what might have caused this? I don’t think I have any new plugins added
Thanks
I’m using both WP to Twitter and the Broken Link Checker plugin (http://wordpress.org/extend/plugins/broken-link-checker/). When I use Broken Link Checker’s admin panel to fix broken links on my site (either by manually entering new URLs or the automatic “fix redirects” feature), the posts with corrected links get tweeted. “Update when a post is edited” is unchecked, and, as expected/desired, W2T doesn’t tweet edited posts when I edit things manually.
Otherwise 100% satisfied — thanks for a great plugin.
WP3.0, Linux/Apache
@carley - import them with draft status, then they won’t tweet, and you can stagger them out as scheduled posts and publish.
Gaz
hmmm…. just realised the above (csv import of posts) may also not work due to the url shorter! Going to give it a go though
WP 3.0
Linux
no problem really….just a query!
I have a new website & plan to upload my wordpress data using a csv…so far the plugin works well when I add my listings individually.
I have yet to try a csv upload however my 3 concerns are:
1. all the new-item tweets go at the same time (eg 30 tweets at once!)
2. no tweets are sent
3. the site sees every item in the csv as being “updated/edited” & tweets all items; new & old (ie even if no actual changes have been made other old items in the csv are tweeted)
Is there a way of setting the plugin to delay the tweet randomly eg 0-300minutes?
Has anyone used this plugin with a csv upload to create posts?
Thanks in advance!
What does “Change Twitter-compatible Service” do? Not sure if/when it should be checked.
Thanks!
I installed WP to Twitter in a WordPress 3.0 blog and couldn’t get Twitter updates with Twitter as a secondary service working. The Twitter-compatible service I switched to was Identi.ca and WP->Twitter was able to send a status message to my account there.
Versions are:
WP: 3.0
Apache: 2.2.9 (Debian server)
PHP: 5.2.6
WP->Twitter: 2.1.3 (latest available from WP plugin repository at the time of writing)
For clarity: I haven’t tested this on actual posts yet, this is the output of the “Check Support” button not working. It works when I’m only using Twitter, but not when I want to use another Twitter-compatible service *and* Twitter.
Obrigada pela resposta Joe, eu estava com o mesmo problema que o Haroun Kola.
Já desativei aquela opção e deu certo!
WP 2.92
I keep getting this when I click on check support
“WP to Twitter was unable to contact your selected URL shortening service.
INVALID_URI
WP to Twitter successfully submitted a status update to your primary update service.
Your server should run WP to Twitter successfully.”
For some reason I’m consistently getting this error.
The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues.
However, sometimes it actually shortens it and sometimes it doesn’t. I’ve verified my settings and either I’m blind to something I’m missing or ???
I’m running WordPress 3.0 and using bit.ly as my shortener. Verified my username and API code also. New install of plug-in
Using Apache version 2.2.15 and PHP version 5.2.13
Thanks
Hello. Using version 2.1.3 of the plugin with WordPress 3.0.
For the first few years of my site, I was the sole poster of content. Recently upgraded some users to “Contributor” status to help me with publishing some older articles which originally appeared on a previous incarnation of the site.
I don’t want these old articles showing up on Twitter as “news” because the posts are from 2002. So I instructed my helpers to check the “Don’t Tweet This Post” box.
When I login to review/approve the articles, the usual “jd_tweet_this” field appears, and the value is “no”. So far so good. However, the “Don’t Tweet this Post” box is now unchecked — and if I don’t recheck it, the article gets tweeted, even with the “no” value there.
So ultimately, I still have to re-check that box before publication, even though it was already checked by the Contributor who originally created the post.
Any way to alter the plugin so it knows that “no” means “no” and to keep the “Don’t Tweet This” box checked?
Normally, this is a wonderful plugin — most of the time when it requests an upgrade, I’m stumped as to why, as I’ve never noticed mistakes or bugs. And I probably would have never noticed this particular problem if I hadn’t started allowing Contributors to help me post content.
Thanks in advance for your time and assistance.
Thank you so much Joe for great plugin.
I was installed on 12 my wp 3.0 based blogs and work perfectly but with too many errors:
There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.
I checked all my blogs today and found that on few of them your plugin sometimes stop to post tweets to my twitter account.
I have one autoblog with posting new articles every 15-20 minutes and found that your plugin was stopped posting to twitter more than 10 hours ago. it’s mean that my blog was u.dated with 40-45 messages but twitter accoent left without tweets.
After clering message “There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.” your plugin follow to post new tweets.
I read too many comments there and found that many people got same error in autoposting mode.
I like your plugin so much but how we can solve such kind of errors ?
Kindest regards and hope you will find right solution.
Eduard
I have a similar issue to recent posters, whereby having upgraded to WP 3.0 and wp-to-twitter 2.1.3, I’m now getting tweets generated every time I adjust a post’s metadata (e.g. change a category or switch comments on / off), despite that fact that my wp-to-twitter settings disallow tweeting on post edits. (“Update when a post is published” is the only active setting).
WP version: 3.0
Plugin version: 2.1.3
Server: Apache/Linux
Installation: Upgrade from previous vers of WP
Whenever I make a post I get the following message:
“There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.”
And on the WP to Twitter settings page it gives me the following error:
“One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!”
What do i do?
I just realize my WP to Twitter appears to be tweeting articles a second time when I update them to change them from being the sticky post to a post that isn’t sticky, but not when I make other changes.
At least I think that’s what’s happening.
FYI: I’m already using my pach from my last comment, but I now have the problem that every post is published to twitter twice. Once with the “original” shorturl “…?p=123” and once with my own URL shortener. Still investigating…
Hi,
After a post failed to be tweeted, I used the ‘Check Support’ button to see if there was a problem with the sever setup, and got this:
“Twitter returned this error:401 Unauthorized
Your server does not appear to support the required methods for WP to Twitter to function. You can try it anyway - these tests aren’t perfect.”
My host is pretty good at making adjustments to the environment if I need them, so I’m wondering if you could tell me what I should be asking them to check?
Thanks,
Scott
Wordpress 3.0
mySQL 5.0.91
PHP 5.2.13
I’m running
Wordpress 3.0
mySQL 5.1.47
PHP 5
Same problem as several above, edited posts are tweeted after upgrading to 2.1.3 today although settings are not set for that. Also, they are tweeted as if they were new posts, (not with any different text added to note like “Post Edited:”)
Nothing was changed today other than the upgrade to WP>Twitter 2.1.3, we had upgraded to WP 3.0 some time ago.
Running
Wordpress 3.0
mySQL 5
PHP 5
Hi Joe - hope you don’t mind me jumping in with this, it’s something I’ve recently found to be having effect with various things in my WordPressing activities.
Could everyone posting about bugs and errors please be sure to state the PHP version their host or own-server is using?
There were MASSIVE changes between PHP 2.8 and PHP 3.0 in the core code, functions, classes, and pretty much most everything, and they might be affecting WP-to-Twitter in unexpected ways, particularly given the huge list of WP functions deprecated or added for WP 3.0.
Just two examples - in PHP the all new DateTime class is going to radically change programming anything that involves the difference between two dates or times (make it a lot simpler and easier). In WP the post_thumbnail function is deprecated. These are just two off the top of my head. There are very long lists of such changes for 3.0 of both PHP and WP.
Although most hosts are running a PHP 2.x version, many are catching up and upgrading to 3.x and I know that utility suites like WAMPserver and XAMPP use PHP 5.3+ which means if you’re site building locally then uploading to hosts, you may be developing under completely different PHP environments, and building sites that rely on functions and classes not available in the webhost server’s PHP - watch out for that one and check the changelist at php.org
— —
A few people have said the non-shortening errors in various forms have only appeared for them since WP 3.0 - to me this implies it is less to do with the new WP or with WP-to-twitter, than it is to do with the subconscious habit of many people to revise their entire plug-ins list when a major WP version change occurs. When they do this, they may be introducing new (to them) plugins that are introducing a conflict scenario.
To all the people only seeing the error since WP 3.0 - please could you list the names of any plug-ins you now have, that you did not have in WP 2.9.x?
We all know of the horrible RSS sub-system errors that WP had a few versions back. For me it highlighted several areas of server stress where WP intereacts with external systems - not just RSS, API calls and API submissions too. They all seem eminently capable of knocking each other around if too many of them are running - particularly if they all rely on WP-cron, which in itself relies too heavily on site traffic.
WP-cron, and it’s counterpart in the SMF forums script that is “lovingly” referred to as “fake-CRON”, has caused more hosting account suspensions than all the hackers in the world put together. It is dangerous to over-rely on it - always try to use real CRON jobs for scheduling periodic tasks.
The CRON systems do not directly tie to WP-to Twitter but might be resource shepherding in that WP-cron needs on-site activity to trigger, and will keep triggering every 10 minutes that there is on-site activity. A site owner writing posts, saving drafts, and publishing, is on-site activity to WP-cron, and it could be triggering a stacked up batch of jobs simultaneously with the blog writer trying to publish and tweet - - - BOP! Resource conflict kicks in.
- Inventory all your plug-ins that perform periodic tasks, and try to identify if they use WP-cron or some other triggering method.
- Inventory all your Plug-ins making RSS or API calls - including widgets and ad blocks such as Amazon and eBay - that make “freah info calls” at each page load (eBay’s scrolling ad blocks really suck the juice out of interconnections - watch the bottom left browser status bar and you’ll see that up to 50% of page load time is connecting to and retrieving from rover.ebay.com).
- Inventory all your “sharing” plug-ins that provide methods for visitors to share your posts (I love AddToAny but am starting to think it might be part of the cause of the problems with WP-to-Twitter), and am trying to replace it out with direct sharing links on a couple of sites as a test).
The only thing we know for sure is that Joe is not seeing 99% of the errors the rest of us are seeing, and that some of us get one collection of errors, and others get a different collection (with a little cross-over).
Somewhere, there has to be a common factor causing these. We have to find it - for the sake of the sanity of all of us - and therefore we need to start posting info to help narrow it down.
As I said at the top, stating your hosting PHP version is likely as good a starting point as any, PHP 5.3 has been around a long time, but a lot of hosts have not moved up to it.
Plug-in conflicts have a long history in the WP world, and not enough has ever been done anywhere to catalogue them, even if individual developers do keep lists of what doesn’t work with their own offering. It may be that we are all using a plug-in that Joe doesn’t use - we need to ID it if that is the case.
Sorry for the sermon - I just see so many short posts and comments seeking help, without helping Joe to know what’s happening. Remember the old sarcasm - Man walks into the doctor’s and says, “Doctor, I’m sick”. The doctor replied, “So am I … of patients who don’t tell me their symptoms”. Don’t be the patient who refuses to assist the physician with their own cure, is what I’m saying.
Gaz
I have set Limit Updating Categories and WP to Twitter doesn’t update ever. Any idea what to check to see what’s up with that? If I don’t select any categories, and when I run the compatibility checker, it tweets fine.
I’m having the same issue as Bill and Marieke… I have my WP to Twitter set to only tweet new posts. That’s what it did before I upgraded to WordPress 3.0. But now that I’ve upgraded, it retweets posts every time I edit them, and I don’t want it to. Help!
WP 3.0
Same here as Bill has experienced. I only want to tweet new posts, but when I edit posts (published on 2.*-wordpress), the posts are tweeted again!
@Daniel15 It’s not implemented yet, and won’t be prior to the OAuth version.
@Jim Hohl I’ll look into the category posting — I’m not aware of any problems, but there may be changes in version 3.0 that I didn’t catch. As far as including your Bit.ly URL — is the string
#url#in your status update template? If it is, let me know - I’ll want to investigate that.I’m using WP3.0 on Apache/Linux, new installation. I have two issues: 1) I’ve set WP to Twitter to only post for certain categories. However, it is posting for EVERY category anyway. 2) Also it is not including the bit.ly URL even though it is generating it and storing it in the custom field.
If you do what Dominik said and implement the WordPress 3.0 URL shortener code (wp_get_shortlink), you could totally remove your URL shortening code some time in the future, and just rely on people to make WordPress plugins for URL shortening with bit.ly and cli.gs. I’ve got a three-letter domain name so wrote my own plugin to make URLs a bit shorter (http://dan.cx/b75 instead of http://dan.cx/blog/2010/04/favourite-web-development-blogs/) and implemented Dominik’s change so WP To Twitter uses these URLs
It may already be implemented, I haven’t checked the latest version.
@Nicholas Ward - Without looking at the code, it seems to me that your change shouldn’t cause any problems - and make actually be what I intended… I’ll have to take a look, but I have a feeling that I may be incorporating that change. Thanks!
I only want a few of my posts to go to Twitter. Perhaps 1 out of 5. I checked “Do not post status updates by default,” which set jd_tweet_default:1. Unfortunately, I would still have to check the box each time I created a new post.
I changed the AND to OR on line 854.
if ( get_option( ‘jd_tweet_default’ ) == ‘1’ || $jd_tweet_this == ‘no’) {
It seems to be working as expected. Are there any problems this might cause?
WP 2.8.6, WP>T 2.1.3…
When I change the Category on an old post, it tweets! Why? I have *only* WHEN PUBLISHED turned on (not WHEN EDITED), and additionally have DO NOT POST BY DEFAULT.
Note these are “old posts” prior to recent install, if that matters.
— bill
Ah, good to know, thanks. I will uncheck all the boxes and see how that goes.
@Dorian I’m not certain why you’re getting the unserialize error, but I would point out that if you want to tweet all categories, all you need to do is leave all categories unchecked - that disabled category controls. When all categories are unchecked, there’s a note at the top of the section stating that category controls are disabled.
WP 3.0
WP->Twitter 2.1.3
Linux
New Installation
Settings > WP to Twitter > Limit Updating Categories
I want the plugin to post all categories so I select all of the tick boxes, click ‘Set Categories’ and it returns a message saying…
Warning: unserialize() expects parameter 1 to be string, array given in /home/at/public_html/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 1033
@sylehc I really don’t think that it’s possible to send a carriage return to Twitter (they just collapse the space,) so it’s rather irrelevant whether you can include one in WP to Twitter. Unless what you’re trying to include is the carriage return character — ¶ — in which case you should simply be able to type it into the field.
Hello, is it possible to add a carriage return between #title# and #url# or in general use special characters?
Thanks for support.
Hi Joe,
OK, this is strange. After I posted my previous comment, I tried to install WP to Twitter to the other WP site. And insterestingly, both Twitter update and Bit.Ly access is working. So I go back to my main site, and checked, and voila, both Twitter and Bit.ly are working. So perhaps there’s and intermittent error somewhere.
Just to be in the safe side, can you still show me how to check the Bit.Ly error code that you mentioned? So next time when I hit an error, I can immediately share the error code with you.
Hi Joe,
I can’t find the “settings export area” that you mentioned. Can you give the location, on which menu? Or should I go directly to the database?
As for the list of plug-ins, here they are: Akismet, All in One SEO Pack, Amazon Product Ads, Amazon Reloaded for WordPress, Amazon Showcase, Easy AdSense, Google Analyticator, Google XML Sitemaps, Popularity Contest, Sidebar Login, SimplePie Core, SimplePie Plugin for WordPress, Sociable, Tweet Blender, Wordbooker, WordPress Download Monitor, WP-PostViews, WP-Print, and of course, WP to Twitter
It’s a long list, I know. I have another WordPress site that I can play with. If you want, I can disable any plugins except yours to test. It’s in the same server. I have not used your plug-in there, but it’s an easy setup, so shouldn’t find any issue.
Hey guys,
I’m using WordPress 3, Linux Hosting [GoDaddy] and I recently upgraded [don’t know the version, but I update regularly] - if there’s updates - I apply them.
The plug-in is installed and WORKING [sending twitter updates like it should], but I’m not able to adjust the settings in the collapsible settings section isn’t working for me. I click on the options and nothing happens; the settings sections aren’t dropping down like they used to. I’ve tried this test with Firefox and Internet Explorer- same issue.
Anyone else having this issue?
If not, any ideas? Thoughts?
Thanks in advance…
Until next time,
LEHenryJr
@Irving My focus at the moment is on OAuth changes, but the shortener API issues are unrelated, so I am interested in anything you can tell me! There’s a field in the settings export area which will provide you with the most recent Bit.ly error value - is there anything there? I’m wondering whether it could be related to another plugin, even - if you can let me know what plugins you’re using, that might help.
@Patrick The OAuth implementation deadline has been shifted to August - so there’s more time than you think. There have been changes in how OAuth will be implemented in open source Twitter clients, so I’m waiting to see how the dust settles.
@Haroun You can disable the global error messages at the bottom of the advanced settings area.
@Dominik Thanks for your suggestion! I have thought about it, but time has been short.
@Michael I’m not sure that feature would really mean anything — do you mean have a status update when you upload an image using the WP media manager?
WP 3.0 on Linux, upgrade from WP 2.9.
The last time I blogged (around April), everything works fine. Yesterday, I upgraded WP to 3.0, upgrade all plug-ins (including this one). And then I put 1 blog.
The status went to Twitter, but not shortened. There is an error in WordPress admin dashboard saying that WP to Twitter have problem contacting the URL shortener service.
I checked and rechecked all settings, even deleted and re-install the plugin. I tried both Bit.Ly (what I use before) and Cli.gs (tried it after seeing this error), and both get the same result.
I can see from your Changelog that you heard about this issue, but can’t replicate. I’m a developer myself, so if you need anything to try to replicate the issue, I’d be happy to help.
Or perhaps you’re focusing on the oAuth changes? Then I’ll wait until you’re ready to debug =)
— sorry, I should have read the earlier comments. Good to know you’re working hard on the OAuth implementation, thanks!
Just adding to ‘Michael Eh?’s comment - I’ve just read on the Twitter API that
“As of June 30, 2010, basic auth (directly passing a username and password for every API request) will no longer be supported. Web applications are encouraged to use full OAuth to authenticate users and act on their behalf…”
— that’s less than a week away!
Read about it here:
http://dev.twitter.com/pages/auth
I’ve had a quick look into the plugin, and it doesn’t look like it’s using OAuth yet, but correct me if I’m wrong!
This plugin works exactly like I want it, just one small problem, I’m still getting the “There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.” and can’t find where to turn this error message off.
Not a disaster, just a slight nuisance
New version works well with Version 3.0 of WordPress. I’m pushing this plugins to my friends. However, twitter is changing to OAuth in August. Is this or future update handle this change over?
Any chance of also having other services like twitpic or it’s like as an added feature to post pictures from the blog to the tweet?
For using the new internal WordPress ShortURL functionality you could just extend the switch…case that selects the shortener:
case 4:
if (function_exists(‘wp_get_shortlink’)) {
$shrink = wp_get_shortlink($post_ID);
} else {
$shrink = get_bloginfo(‘url’) . “/?p=” . $post_ID;
}
break;
Have you ever thought about moving the shortener into a function you call with apply_filter(), i.e. kinda allow “plugins for your plugin”? I believe that would make the code much more legible and extendable. And you wouldn’t have to bother about all the people who want to use their own URL shortener. Just allow them to write their own shortener plugin.
@Nick P, @Gabe: The trailing parenthesis on your URL is from your status update template. You can remove it from the template. This is not a WP to Twitter problem, it’s an issue that Twitter interprets the closing parenthesis as part of the URL when it generates the href value for the text.
@Nick P The extra text you’re seeing is an error; I’ve removed it in an update.
@Gabe,
I’ve just checked a tweet I sent this morning and I’m seeing the right bracket on the end of the bitly URL too. However clicking the link still seems to work and takes me to the correct page.
Is there any reason why since I’ve upgraded to 2.1.2 (for WP 3.0) that when I go to the WP to Twitter Account Settings section, to the right of the twitter password field it says:
[redacted]
Anyone else seeing this?
Okay, I found the issue myself (isn’t it great having a developer as a user?
). Postie is using the WordPress wp_insert_post function to add the post. In your wp-to-twitter.php file, line 424 is the following:
if (($get_post_info->post_status == ‘publish’ || $_POST[‘publish’] == ‘Publish’) && ($_POST[‘prev_status’] == ‘draft’ || $_POST[‘original_post_status’] == ‘draft’ || $_POST[‘original_post_status’] == ‘auto-draft’ || $_POST[‘prev_status’] == ‘pending’ || $_POST[‘original_post_status’] == ‘pending’ ) ) {
As Postie is not using POST data, none of those $_POST[‘…’] conditions match. This would be the same with any other script that inserts posts with wp_insert_post() I believe. I’m not entirely sure why it’s checking the previous status (I don’t know much about WordPress code, I mainly use the Kohana framework myself). I wasn’t entirely sure how of the best way to fix it either, so I’ve just edited Postie and added an incredibly ugly hack (postie-functions.php:554):
$_POST[‘original_post_status’] = ‘auto-draft’;
So your if statement matches correctly.
Hope this helps, and I’m looking forward to a proper fix (or some details on what the best solution would be).
Thanks!
Hey Joe,
WP to Twitter does not appear to be working with the Postie plugin. When I post via email, the post appears on my blog fine, but does not post to Twitter. I saw an old forum topic about this (http://wordpress.org/support/topic/238117?replies=5), however it’s from a year ago, and there was no resolution. Is this a known issue?
Thanks!
Hi! Is it possible to change from “WP to Twitter” ?
Thanks in advance!
I noticed the incredible amount of Twitter issues as of late - something about the fail whale or something? It’s odd that this plugin used to work great and then suddenly doesn’t. Good news on the 3.0, thanks!
@Heather: That error might mean that Twitter was having server issues. Twitter’s been having a large number of server issues recently so I would not be surprised.
This plugin seems to work on WordPress 3.0 to me, so I’d say the upgrade should be okay
Hi, I am getting daily error messages, for the past week or so that the Tweet is not posting correctly and I should see if the URL shortener is having an issue. When I click on their sites, they do not mention one.
Today’s error was “One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish! ”
How do I fix?
2- Also, will the upgrade to WordPress 3.0 impact this plugin?
There is a PHP class written specifically for Twitter with OAuth, so that shouldn’t be a major problem. Definitely not going to go the route of using an unusual extension, however — that would be very unsuccessful for a plugin like this.
@Joe
. I’ve written a few PHP scripts that use OAuth, including a bot. I used the OAuth PECL extension though, which not many hosts have installed (I’ve got a dedicated server so I just installed it manually), so maybe that’s not a good approach for a plugin that a lot of people are using. Perhaps there’s a pure-PHP OAuth implementation, I haven’t really looked around.
Ah, I see, didn’t see that post
Didn’t even notice it…I knew what you meant!
@Daniel15 Oh, believe me - I’m well aware of this! The postponement is significantly due to complaints and requests from developers on platforms like WordPress and the unacceptable nature of the original oAuth implementation requirements for this type of tool.
Sorry, I meant Twitter was going to remove *Basic auth* this month, not OAuth. Sorry for the confusion, I need to proofread my comments before posting
@Joe:
It’s working fine for me (just testing it on a test blog and test Twitter account), I just thought I’d mention OAuth since it’ll be essential eventually. Twitter were going to remove it this month but they’ve postponed it to August (source: http://apiwiki.twitter.com/). Come August, every Twitter application that uses basic authentication will stop working, so I’d suggest to change the plugin soon so everyone has some time to update to the new version.
Thanks!
@George, @Ryan, @Daniel15, etc. There are a lot of strange things going on with WP to Twitter at the moment, and this is a priority for me to work on this week. Don’t expect any specific responses to problem reports at the moment — but I’ll be looking at a lot of different issues, and I do appreciate whatever information you can give me.
Hi Joe,
I use this plugin on 2 websites (Obviously using 2 different Twitter accounts). A few days ago the plugin stopped working on both websites and it didn’t send any posts to Twitter. Upgraded both sites to WP 3.0 and the plugin is working like a charm on the site “A” but it doesn’t work on the site “B”. Also when attempted to save the categories under options I got the following message:
“Warning: unserialize() expects parameter 1 to be string, array given in /home/myusername/public_html/mydomain.com/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 1063”
Hello,
Great plugin so far, I like it
Are you planning to upgrade it to use OAuth instead of Basic authentication some time in the future? Twitter are going to remove Basic authentication in the next few months, meaning the plugin will no longer work any more. If not, I might have a go at doing it myself
Wordpress 3.0, new installation of latest wp-to-witter, Apache/Linux
FYI only.. After a local server path in the YOURLS account settings has been set, the interface does not seem able to remove it again. If I blank out the path in the local installation path field and save the account config, the path simply reappears the next time I enter the configuration screen. The blank value does not seem to save.
The reason I had to remove the path to my local YOURLS was permission restrictions between the two installation paths. The WordPress installation cannot access the YOURLS files on a separate domain installation directly (without me munching the virtual host file permissions severely; not your problem
).
So, I tried switching to use a “remote” call to the local server. However, as mentioned the local server path field will not clear after first entered, and apparently takes precedence after it has been set, so URL shortening fails.
here’s my solution — I deactivated all plugins, and I installed bit.ly’s auto-shortener in my browser.
Hi
I have tried reading through these comments first before asking, but I don’t see a clear answer. WP to twitter has never shortened a URL. I always get the SAME error testing.
WP to Twitter was unable to contact your selected URL shortening service.
WP to Twitter successfully submitted a status update to your primary update service.
Your server should run WP to Twitter successfully.
I always get that same error when it updates my posts to twitter. It always posts the long URL on Twitter.
I have tried both bit.ly and cli.gs and have API’s for both. I have tried with leaving both API’s filled and leaving one or the other blank.
I use WP 2.9.2, (will be upgrading to 3.0 soon)
I run on a Linux server
I do not use the standard permalink style in wordpress (not sure if this matters) I use http://www.ambercabral.com/2010/06/sample-post/
Not sure if this matters either, but my Twitter is private.
Hope you can help me
Thanks!
@Dominik Thanks for bringing that article to my attention. Longurl.org is back up now, actually, so I’ll probably just be re-enabling it. I will probably go ahead and make use of the new shortlink features in WordPress, as well.
Two quick notes/questions:
a) Since jd_expand_url() is still disabled, you might maybe interested in this: http://www.phptips.im/articles/php-snippets/retrieve-the-original-url-from-a-shortened-url/ - it’s not too hard to find out where a short url is redirecting (at least in most cases - not true for shorturls that use frames).
b) Are you going to support the WordPress 3.0 “shortlink” feature?
I have used and am a fan of wp-twitter for a while now and in the last couple of months the scheduled tweets are not appearing even after installation. Live posts work fine but all of the others are not going out. Is there something we’re doing wrong?
Thanks for develop this plugin
Hi- no URL at all is attached to my tweeted posts. I tried both cli.gs and WP. I am going through the settings again right now, suggestions appreciated.
new install
WP 2.9.2
linux server
Joe,
I have a few questions. I’m running
WP 2.9.2 with
v2.1.1 of wp2t
on Apache (hosted at hostgator)
After upgrading to 2.9.2,
i’ve been having problems using the url shortening service — its only intermittent, but i’m not sure of exactly why this is happening. Have you heard much about this?
Thanks, Tim - I haven’t had time to actually find the problem and fix it, but I could at least disable the errors for you!
yay! Just found the disable global error messages tickboxes…thanks for doing that and listening
Such great support - wish everyone was like you in that regard. Really appreciate it.
WP Version : 2.9.2
Server : Apache / Win
New installation
Hi !
First ! Nice plugin .
Now my problem :
We use WP as a multi users website, when i post , update , plugin work fine but when it’s one of my teammate (admin too) it won’t work and we have error like this :
“One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!”
Thanks
Hello, I have several wordpress in same Linux/Apache server, in some of them (olders) wp-to-twitter works perfect.
wp-to-twitter 1.5.4 in WordPress 2.8.6 works perfects, test button gives this text:
* Successfully contacted the Cli.gs API via Snoopy and created a shortened link.
* Successfully contacted the Bit.ly API via Snoopy.
* Successfully contacted the Twitter API via Snoopy.
* Your server should run WP to Twitter successfully.
wp-to-twitter 2.1.1. in wordpress 2.9.2 shows me this error:
* WP to Twitter was unable to contact your selected URL shortening service.
* WP to Twitter failed to contact your primary update service.
* No error was returned.
* Your server does not appear to support the required methods for WP to Twitter to function. You can try it anyway - these tests aren’t perfect.
Is the same server in both scenarios.
What do you think should be happening?
@ Joe
Following up what Keichi said earlier about short URL truncation
I was checking server error logs for something else yesterday and noticed a lot of entries for it.ly - I queried it with hosting support because their mod_security was killing access to/from anything associated with that domain. My suspicion was that this was a problem coming back from bit.ly related to WP-to-twitter seeking short urls, and the returned url getting mangled somewhere.
The frequency of errors related to it.ly was about the same as the new posts frequency, but I didn’t check into the times of events (sorry - didn’t think of it at the time).
Not sure if this is coming from the plug-in (or bit.ly) or not, but it’s worth a post-it note on the investigation board, as something that might be related to the problem.
Gaz
I am currently using WP 2.9.2 with the most updated version of WP to Twitter. Last week WP to Twitter started only shortening URL’s for my posts and not my partners. Her posts contain the full URL of the post even though we’re both using the same #url# tag in our Twitter Post box. Any thoughts as to why this might be? The settings have been changed in the admin account, so they should be universal to each of our accounts. (This problem did not start with the upgrade…I only upgraded after I noticed the discrepancy between our tweeted links.) Here are our tweets: http://twitter.com/freshnestdesign Thanks in advance for any help you could provide!
@Gaz Thanks for responding with help. I’ve already spent too much valuable time trying to fix this problem and am now looking for a replacement plugin that will work for me. I have quite a few blogs/websites that I own and don’t have the time to do it manually but since WP to Twitter isn’t working I have to move on. Any suggestions?
Nice plugin
Would you please consider adding su.pr support for URL shorteining?
Thank you,
I need 2 urls for my blog. The regular permalink and a second url for twitter that is slightly different than the permalink created by WP e.g.
Permalink: http://www.mysite.com/blog/?=21
WP to Twitter URL: http://www.mysite.com/blog.php/?=21
Is there a way to automatically create/change the different url in WP to Twitter without changing the WP permalink or Blog address (URL) settings.
WP to Twitter has been working just fine for me for ages, but then a week ago it stopped feeding Twitter. Weird right? Nothing at all has changed, but I now get this error every time I post.
http://www.theblacklaser.net/stuff/wptwitter_error.png
I don’t understand why I’m getting the 401. Everything seems to be in order. Help?
Thanks.
Can you add support for Tinyurl.com, http://is.gd/, http://tiny.cc/,
•Current WordPress Version
2.9.2
•Server Type (Apache/Linux, IIS, etc.)
IIS 7 Windos 2008
•Whether this is a new installation or an upgrade.
New Installation
•If an upgrade, which version you have upgraded from.
•A detailed description of your problem.
When i try edit and post again any post i got ths message:
One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!
With Cli.gs enabled works fine, but when i set to “dont shorten urls” i get this error after try send a edited post
When I do the check in the Settings panel I get the following messages, being unable to contact the Bit.ly service and Twitter seems to be my main issue, I’m not sure what’s causing it.
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.
WP to Twitter was unable to contact your selected URL shortening service.
WP to Twitter failed to contact your primary update service.
No error was returned.
Your server does not appear to support the required methods for WP to Twitter to function. You can try it anyway - these tests aren’t perfect.
I’m using a fresh install of the WordPress 3.0 Beta 2 on an Apache Server; curl is definitely available on the server. Oh and I’ve definitely entered in my account credentials for both services correctly (I triple checked that).
Thanks again.
@Matt C Not a problem. The plugin makes use of the WP_HTTP class in WordPress. This class is designed to identify what transports are currently available and use the best option on your server. So, any method being available should work: cURL, fopen, etc.
The error checking is also checking whether the returned information is interpretable; so if the return is bad, it’ll also return false. There should be more detailed information when you try the check function (bottom of the settings page) which can help — it includes any error message from Twitter, etc.
The whole error checking section is still a bit kludgy — I need to do clean up, but I’m waiting until after I’ve dealt with the whole oAuth issue before I do that.
Sorry for the e-mail before this comment. What methods are required on the server side for this plugin to work?
You have the following in your FAQ:
“What if my server doesn’t support the methods you use to contact these other sites?
Well, there isn’t much I can do about that - but the plugin will check and see whether or not the needed methods work. If they don’t, you will find a warning message on your settings page.”
However I couldn’t find anywhere that you documented which methods are actually required to be able to talk with the Twitter and Bit.ly services.
Thanks for the help.
@Keichi Well, I’ll look. But I don’t see how it could happen — the plugin just doesn’t do anything with the short URL other than fetch it and send it.
@Biff Advanced Settings > Disable Global Errors
I’m still getting constant error messages. Why don’t you just include an option to turn the error messages off?
@Joe i though that at first too… But it didn’t look like it, because all other Twets are looking correct.. It seems like it affects just the ones with a Long title + Hashtags
And of course.. The URLs get rightly added inside the Yourls Admin Interface.
@Keichi I appreciate your note, but I’m afraid I can’t really see a way that WP to Twitter could be causing that problem. WP to Twitter takes the YOURLS shortened URL whole from the application and makes no changes to it at any time. If the URL was missing completely, not shortened, or truncated, I could understand that as a possibility — but this seems more likely to be an error from the YOURLS application. I’ll look around, but I don’t honestly think I’m going to find anything.
I found a Bug in WP to Twitter Version 2.1.1…
The Plugin cuts the Shortened YOURLS URL instand of Cutting the Hastag which why it Tweets this
“Cover Voting für Evangelion 1.11 Bluray Abgeschloss mehr auf: http://Keic.de/s/20 #Cover #Evangelion #Evangelion_1.11 #UFA #Universum_Anime”
Instand of this
Cover Voting für Evangelion 1.11 Bluray Abgeschloss mehr auf: http://Keichi.de/s/20 #Cover #Evangelion #Evangelion_1.11 #UFA”
As you can see there are 2 Letters missing in the URL of the Tweet.
@Dan Mibiliak
In twitter, is the URL showing as domain/blog/full-post-title or as domain/blog/?p=xyz
The reason I ask is that the /?p=xyz (where xyz is the post ID number) is the only shortening WP does natively. When you first auto or manually save a post, you will see a button appear under the title on the edit page that says “get short url” - that gets you a bit.ly style short url from wp.me and you can paste it into the custom field for the wp-to-twitter short url to overwrite anything already there.
(info Joe / Chuck) I notice Dan has the sociable or add-to-any social buttons array on his home and single pages. When I hover over the twitter icon, the url it offers to send to twitter, is the full long url with full post title (I must check if it’s doing the same on my sites) and can’t help wondering if this might be a cause of interference with the wp-to-twitter short url services (conflicting commands on-page / in-memory regarding what to send to twitter)?
@Dan - site marketing tip - I notice you have no link on your site to your twitter account for acquiring more followers - adding a little blue bird somewhere might be a good idea. I had no way to view your tweets and see what the url display was showing.
Gaz
Hi Joe
I am running the latest update to both WP-Twitter and WordPress. It seems none of my tweets are being shortened. I have APIs for bitly and cligs and it’s not working with either. I tried changing my setting to wordpress shortening and it still didn’t shorten my link. Is this a problem others are experiencing or am I doing something wrong. The error msg also says that the post isn’t getting sent to twitter but I’ve checked and they are but not with a shortened URL
Joe - I’m glad liaroms brought up the point about the test and the test tweet, I’d forgotten to mention that - the test tweet shows up on my account regardless of a failed or successful server test, and regardless of a failed or successful url shortening message.
I think there’s a clue in that, that the actual send code in that part of wp to twitter is working regardless. It might be a good place to start a comparison to the rest of the code for these various errors - do the others have something triggering false errors sort of hunt.
Gaz
I have had varied success with this plugin and most of the time I just get the message that WP to Twitter failed to tweet or something like that. I kind of gave up. I just updated today to the latest version, I’m not getting the error messages but no tweets are being updated either. Categories are selected.
When I test the button at the bottom it says my server does not pass the test. I get a test message in my twitter account though? What can I do to get this to work?
WP V 2.9.2
Server type not sure? Linux operating system I think
1) This plugin is a registered plugin with Twitter, and that’s coming from the Twitter registration information.
2) You don’t.
sir, i installed this plugin but there’s is a problem that “via WP to Twitter” is coming in all twitter posts instead of “Via API”, and this links to some website.
how do i change it?
thanks in advance
My template is this:
#title# (#url#)
Is your template actually
(#url)? If so, that shouldn’t work at all - it should be (#url#). However, I have heard this problem before, so I’m guessing that’s not it — I’ll have to look around though to remind myself what the solution was. Adding a space shouldn’t be a problem.Twitter ID: ipads_4_free
I use WP-to-Twitter plugin and love it. However, all of my bit.ly URLs are having the trailing ) added to the URL - my template is (#url). As a result none of the links work when clicked. For example, the bit.ly URL should be http://bit.ly/deA216 but instead it is http://bit.ly/deA216).
I know enough PHP to fix this if I knew where to look. Also, could I fix this by simply adding a space btwn #url and ) or will this get trimmed out?
Thanks
@Paul Activating and deactivating plugins does not run the uninstall routine for the plugin; the only way to do that is to delete the plugin from the WordPress plugin manager. So yes, if you haven’t actually deleted the plugin using WordPress, then older settings have never been deleted.
@everybody This problem may or may not be fixed. I appreciate that @Paul mentioned that he was able to successfully use version 1.3.7 — that’s almost the first useful piece of information I’ve received about this problem.
Same thing with the error- and duplicate tweets. Ironically, the newest version of this plugin is completely broken - and the only version that works to some degree is 1.3.7.
Maybe it has something to do with activating / deactivating different versions back and forth? Perhaps a database corruption?
I only say this because - when I tried the 2.1 version (with bit.ly support) it didn’t work - but when I reverted back to 1.3.7 (which has no bit.ly) - it would sometimes ping Cli.gs - and sometimes bit.ly - even though it’s not in the older version.
So it’s picking up configuration settings from somewhere… any way to cleanly de-install - and re-install fresh?
Thanks!
Still doing the error thing, solved it for a while, it’s back again and definitely has the ‘reset to Twitter settings’ thing correct, I just checked and redid it - no change.
Can’t I just disable it? It’s hella annoying and those across-all-pages alerts should be for OMG IT’S GONNA EXPLODE! DO IT NOW! END OF THE WORLD! type errors from a UI/IA standpoint, rather that a post hasn’t made Twitter (allegedly, but seemingly falsely) - it’s not the end of the world anyway?
So still a vote for disabling it/hacking it to shut up…
I’ve got a strange error too.
I used WP since january in my small blog. It worked really fine.
But since yesterday I began to have errors:
“There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.”
Everytime I update or post something new an error appears:
“One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.”
I have last wordpress version, last version of WP-to-Twitter and have chenged this plugins:
Installed teetme by error, Confused it with Tweetmeme.
Installed Tweetmeme, errased Tweetme.
When I thought Tweetmeme & wp to twitter worked fine, no updates were posted.
I uninstalled Tweetmeme in case it makes any incompatibility issues.
Errors are still there and no updates are posted.
I’ve got Wp-super cache installed too…
Can anyone Explain what can be happening?
Thanks a lot, sorry about my english.
How can I disable the error message that shows up ‘There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.’ I would rather not see it.
Hello Joe
just started receiving these error messages today. I have not made any upgrades to my WP or Server. Things were looking great through out the year up until today. (godaddy vert. dedicated server / linux) Any suggestions ? Thanks much.
Failed to contact the Cli.gs API. Successfully contacted the Twitter API. Your server does not appear to support the required PHP functions and classes for WP to Twitter to function. You can try it anyway - these tests aren’t perfect - but no guarantees.
The query to the Cli.gs API failed, and your URL was not shrunk. The normal post URL was attached to your Tweet.
Cli.gs request failed! We couldn’t shrink that URL, so we attached the normal URL to your Tweet. Check the Cli.gs blog to see if there are any known issues.
@tiagojpovan - did you see my earlier post about simply “updating your post” after getting the error, and it then tweets normally?
It’s not a fix, it’s a temporary workaround that works for me, it might work for you too.
I’d also like to remind everyone of what Joe said in his last post - PLEASE READ
The Future of WP to Twitter
http://www.joedolson.com/articles/2010/05/the-future-of-wp-to-twitter/
YOUR input is needed by Joe - give him back some of the support he’s always given to you.
Gaz
I have the same problem reported by @chrisaceto a few post ago. Any news about this?
@Biff
Somewhere earlier in the comments here (or might have been in the WP forums - search for the plugin name there), I did see a comment that stated which lines in the plugin php file to comment out to suppress both the warning message, and the call to visit the settings to clear the message.
Sorry, cannot remember which site it was on, but I did see it - honest.
@Dbaglady - Google “http error 401”
It will provide everything you need to know.
To quote a well known authority on such topics -
The Web server (running the Web site) thinks that the HTTP data stream sent by the client (e.g. your Web browser) was correct, but access to the URL resource requires user authentication
1) which has not yet been provided
or
2) which has been provided but failed authorization tests. This is commonly known as “HTTP Basic Authentication”. The actual authentication request expected from the client is defined in the HTTP protocol as the WWW-Authenticate header field.
Generally this error message means you need to log on (enter a valid user ID and password) somewhere first. If you have just entered these and then immediately see a 401 error, it means that one or both of your user ID and password were invalid for whatever reason (entered incorrectly, user ID suspended etc.).
…… which in plain geeklish translates to “PEBKAC”
I got this message: Twitter returned this error:401 Unauthorized
DOES ANYONE KNOW WHAT IS MEANS AND WHY!! OR HOW TO FIX IT????
Isn’t there any way to turn off the pink error notification banner? Shouldn’t that be an option? Everyday I get errors. I don’t need to hear about them.
Thanks Joe
So that’s not the issue? Back to hunting the bug.
I did notice by accident earlier - if you’ve got a post that spawned the error about not sending, then simply update the post, it sends flawlessly.
This sort of hints that the error is sat solely within the initial short URL acquisition routine and initial sent to twitter - could it be a time-out issue? Is the plugin not giving the shortening service enough time to reply before moving onto to actually publishing the post? There seems to be no problem once it’s already got a short URL.
Gaz
@Gaz All five of those custom fields are pretty long-standing; jd_tweet_this is pretty obvious, but the rest of them are as follows:
jd_twitter: contains the template used for the tweet;jd_wp_twitter: contains the text for the tweet, only used if WP to Twitter reports a failure to post to Twitter;wp_jd_target: currently only semi-functional, used to contain the full URL which your short URL points to. Ceased functioning when longURL.org was shut down, not yet replaced; for the moment, it’s just receiving the short URL.wp_jd_wp: Contains the short URL; is specific to which shortener you’re using. (_wp is WordPress, _cligs is Cli.gs, etc.)@Bud Green Can’t say what’s going on, exactly, but this is what Google says: http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=164577. Why they’re picking up YOUR post I have no idea; but it’s unrelated to WP to Twitter — those duplicates are not being posted by the plugin. You can tell from the source link on the status update.
@chrisaceto I might look into that, but to be entirely frank, revising the Twitter status posting methods is an extremely low priority right now, given that they’re going to have to be gutted and completely re-done within the next month anyway.
@everybody Please, read this: The Future of WP to Twitter
I’ve tried 3 other post to twitter plugins and all three worked perfectly. Unfortunately, none of them have the same great features WP > Twitter.
I really hope this issue gets resolved soon as I would love to use this plugin!
“One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!”
Seems like google has hijacked my tweets @calpotnews somehow. Every WP-to-Twitter post appears twice, one with a bit.ly URL and the second with goo.gl. Suppose that’s twice as nice, in one sense, but annoying in another. This just started; plugin was working great before. Current WP install.
Jooooooooe
Following up more on this problem with the post publishing error message “There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.”
On my oldest, biggest, and until now my most stable, install, I’m getting the error message there too now. But I also noticed something odd in the post page custom fields table that I never noticed before … it’s entering 5 (FIVE) custom fields for wp-to-twitter …
jd_tweet_this (yes or no) - this has always been present since way back when.
jd_twitter & jd_wp_twitter - both with identical tweet content (140 character thing)
wp_jd_target & wp_jd_wp - both with WP short url (site/blog/?p=1234)
Seems to me that maybe somewhere you’ve renamed some variables or database columns, but haven’t removed ALL of the old naming system. Or is this by design for multiple posting services?
Gaz
@ Joe
The RSS to facebook is from within facebook (not a WP plugin or function) -> from your facebook wall (home) page click the edit page link at top right just below your avatar. On the page that opens, scroll down to Notes and click to edit settings (or something) - if you haven’t yet set up a blog import, it’ll offer you a box to add the feed url from whichever source you want. If you have one already, and want to change it, you have to delete the existing one then add a new one.
It then imports about twice a day using normal import processes for feeds, and posts to your wall, or your facebook page created for your site/business/club/whatever, depending on, on which page you set up the feed. If to your personal wall/profile, it echoes the post to all your friends walls. If to your biz page, it echoes to all that pages fans’ walls.
Right now, I’m having to work with the assumption that wp-to-twitter is adding/amending something in the post properties, which is causing the feed to fail. I’m trying to find time to cross check against other feed importers to see if it’s universal, or if it’s restricted to facebook and our newsletter server that uses feed aggregation. I’ll keep you updated on this.
@mpmchagh -> re: author accounts
Not sure if this is still applicable, but a few versions back - if you set the wp-to-twitter option that authors had their own twitter accounts, then when a post was tweeted, it would tweet as normal on the blog owner’s twitter account, AND retweet to the author’s twitter account with an “@author” retweet prefix before the normal tweet prefix (new post: or whatever you have it set as - e.g. the tweet would start as “@author RT New Post: blah blah”)) - not a 100% ideal retweet / tweetecho, but 99% good enough for us.
I can’t verify it’s still doing this as all my wp-to-twitter installs are broken since upgrading.
Gaz
For some reason every time I publish a post I receive the error:
One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!
It posted 2 or 3 times and now for some reason it has stopped.
Thanks for the quick reply!
Yes, when auto tweeting is turned off, the checkbox remains “Don’t Tweet this post.”
Not sure how I missed the category stuff. Thanks for pointing it out.
Did you see my authors account question?
Thanks,
mpm
@mpmchugh That is what the disabling of auto tweeting should do — I may have broken something there in the last update…I’ll review that code. As for category restrictions, yes - that’s the bottom panel on the settings page: Limit Updating Categories.
One other question… is there a way to exclude certain categories from auto-tweeting?
Not sure if I’m just missing this, but is there a way to set WP>Twitter to be more manual, i.e. having to check a box to tweet when published, as opposed to unchecking a box not to tweet? I turned off the auto tweeting for posts, thinking the check box would reverse its purpose, but it did not.
It’d be nice to have a “Tweet This Now” button available if the auto tweeting feature is off.
Also, regarding Author Twitter accounts — do posts by authors with twitter account only get tweeted to their account? I assume so, but want to confirm.
@Gaz You’re the first person to mention to me the fact that WP to Twitter seems to be generating short URLs on draft saves - that’s an important piece of information, and shouldn’t be happening. I’ll take a look.
What exactly is the RSS to Facebook tool? WP to Twitter shouldn’t even have a possible way to mess with any form of RSS output, but I’d like to know what tool you’re using to post to Facebook, so I can look at it.
wp.me is a legitimate WordPress URL shortening tool, so it’s not a hack thing - but my understanding was that it’s only available on WordPress.com hosted blogs - if it’s coming into use on the self-hosted software that’s news to me, too.
@Tim You know, this is a problem that’s just starting to bug me. It seems like if I fix it for one group of people it always breaks for another, and I don’t know what’s going on. I’ll email you; I’d like to follow up on this.
oh I’m using the latest version, updated via the WP update system….it’s been doing this on the old version I was running too.
Current WP version 2.9.2, server is Apache/2.2.15 (Unix) and I dunno which version I upgraded from, something many months old.
Firstly thanks for a great plugin! Really love it!
Is there anyway to permanently disable the nag error screens:
‘There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.’
I’m getting false alarms with every post I tweet, it just annoys me that message - I don’t want to have to ‘clear’ it I’d rather it just went away.
Or fix the problem, but all the settings seem correct - it says
‘One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure.
Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!’
when it has actually posted it.
Is there a hack to disable this error?
Hi Joe
(one of these days I’ll remember to put the correct web address when posting a comment)
I’ve verified the wp.me button is in othere WP 2.9.2 blogs too - it’s not there when you first go to add a post, but after you click to sacve a draft, it appears alongside the button to edit the post slug (under the post title box / above the button bar for the editor). I’ve now seen this on multiple sites on two different servers in the UK & US - one Unix/Plesk, the other Linux/cPanel, which sort of says it’s coming from within WordPress, not the OS.
I’ve not been into my sites today that have never had WP-to-twitter, but on the site where I deactivated and deleted the plugin, the get short URL button persisted and continued to return the short URL. I haven’t tried browsing to wp.me - I keep wondering if there’s a hack been injected to cause this, as I remember nothing about it from wordpress.org announcements, but it’s on everyone of my sites so far, and a really “out of the box” thinking by a hacker if that’s what caused it.
The RSS problem is now demonstrating on all sites that were previously feeding to facebook pages with the plugin inactive, as soon as it went active, the RSS to facebook stopped. Strangely, on at least one of the same sites, the RSS to the newsletter server continued being picked up, but only from one site (the newest of the bunch).
The site showing the database disconnect is on a new cloud hosting service, and it’s repeated once or twice since removing the plugin, so it may be teething troubles with the cloud config, I’m waiting that one out to see if it persists. A couple of screen refreshes usually clears it - I’ve seen similar database stutters on windoze and linux hosting before (but almost always with UK hosts for some strange reason).
There’s no denying there is a genuine issue with the URL shortening kicking up errors at post publish time. I’ve also notice on those sites where the plugin is still active, that saving as a draft creates a short URL in the custom fields on the create post page - it never used to do that before.
It only ever used to try to get a short URL at the time of posting - whether immediate or scheduled - I think this may hint as to where the issue is coming from - some of my drafts are up to 16 or more repetitions of the same short URL in the custom fields list on the post edit page.
(I do a lot of drafts and regularly rework them before publishing - I know many people don’t, and maybe this is why I’ve spotted these issues when others haven’t).
Gaz
@Gaz I’m sorry to hear that, but, to be entirely honest, I’m not 100% convinced that WP to Twitter is actually the sole source of these problems, largely because of the thousands of users of the plugin, you are the only person to be reporting a problem with an RSS problem or the database disconnect. There may certainly be problems with the plugin and your host, but I can’t say what they might be.
I’m curious about the wp.me shortening button, though — I don’t have that in any of my installations of WP 2.9.2, so I’m a bit puzzled where that’s coming from for you. I feel like there’s some piece of information I’m missing here.
Also, there’s really nothing stopping you from just using an older version, if those were versions you were happy with. Most of them are available for download from WordPress.org.
@We / @Pitchers - Could happen at some point. Restricting secondary authors Tweet content seems likely a potentially good idea, and wouldn’t be that difficult to implement.
I could NOT get it to work properly after the error messages started to appear. Nothing worked to fix it. So I deactivated and deleted. THEN reinstalled, activated and configured. Been working fine ever since.
Hi Joe
Still no success getting tweets to send without an error message in WP admin - whether a new post or a revision, it’s returning the same error every time on the site linked in this comment (and all my others too).
Sorry to say it, but I really am at the point of giving up on wp-to-twitter.
There’s several other factors involved too - I notice (only just now - duhhh - must be going blind in my old age) that next to the permalink edit button in WP 2.9.2 is a button to get a short URL, which is provided from wp.me domain - looks like WordPress is moving in on bit.ly et al.
Also, on this site, I’ve noticed any attempt to post to twitter when creating or revising a post, causes a database disconnect immediately afterwards. That I cannot allow to continue in case it triggers a resource abuse event at the hosts and gets the account suspended.
Seems like you’ve got some very deep rooted issues in the plugin now you’ve added those other shortening services. If it were me, I’d be ripping them out and rolling back to the point of just bit.ly and cli.gs when it all worked, then rebuild from there.
Sorry mate, I’ve loved the simplicity of use of wp-to-twitter for years, but cannot continue like this - it is heavily impacting my blogging rate now, and that affects my income, so it looks like it’ll have to go.
Also the problem previously mentioned, that RSS feed output fails since wp-to-twitter two versions back, continues and that is a crucial part of my marketing mix. Your plugin has to come off the sites until its guaranteed fixed and working again.
Best of luck
Gaz
Joe,
Fantastic plugin. I was wondering if there were any plans to configure the tweet options from the administrative end, including restrictions on what the wp-to-twitter content would be.
eg: website twitter account to send tweets, but the individual users accounts (provided they’ve added their credentials) would send out the same tweets as the parent account.
In our circumstance, we try to restrict authors to solely authoring content and automating as many parts of the editorial process as possible.
Is it possible now, or would it be possible to add in the future, the ability to send a tweet to multiple accounts when a new post is published?
For instance, we have three authors at my site, and it would be beneficial to have a tweet from all three accounts when a new post goes up.
Thanks!
Hi Joe, looks like the error messages calmed down for me. Thanks for all your help!
Hi Joe,
Ok, I saw that last night and checked it, but today it is still coming up on posts I compose as unchecked, so it for some reason is still defaulting to post everything to Twitter. I can manually change it each time, but it’s going to take some getting used to. Not sure what the issue is. Not a huge deal in the scheme of things, but hopefully it will get back to the way it used to be at some point.
Thanks again for the great plugin.
Hey Joe, this was the error message from today’s post:
The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues. [Cli.gs Blog] [Bit.ly Blog]
Like the others stated, when I log into bit.ly it shows a shorten url for today’s post, but on twitter it is the un-shortened url.
It has been going on since earlier. I try to switch to bit.ly after every new release of wp to twitter, but it has always given me the results that Anne, Sal, Grendel and RadekI are having, so I switch back to using cli.gs. I would like to use bit.ly
@Sister Toldjah The option is still there, under Advanced Settings, and shouldn’t have changed under the latest revision; although there were some changes made to bugs with that system which could have caused some changes for you.
Thanks!
@Sean Interesting - no error message. Did this just just start with 2.1.0, or has it been going since earlier than that?
Hi - I’m using WordPress 2.9.2 and the most current version of WP to Twitter. LOVE this plugin, but it appears that once I updated this plugin, the default in posts is to send to Twitter and I used to have the default set not to send to Twitter so I could select what I wanted to send. Didn’t there used to be a setting in the WP to Twitter options to set the default on all posts to NOT post to Twitter? I am not seeing that now. Thanks in advance …
This is what I get when I hit the “Check Support” button:
* WP to Twitter was unable to contact your selected URL shortening service.
*
* WP to Twitter successfully submitted a status update to your primary update service.
* Your server should run WP to Twitter successfully.
What happens if you use Check Support option? Is any error reported?
Hey Joe, I’m having the same problem as the people below:
I’m having the same problems as Sal, Grendel and Radek - error message saying unable to shorten (“The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues. [Cli.gs Blog] [Bit.ly Blog]”), and the twitter output is not shortened, but bit.ly history shows the request was received by bit.ly and a short URL produced.
Currently using WP 2.9.2
wp-twitter 2.1.0
Thanks for the quick response! I’ll check to see if I get any more errors over the weekend.
@dismal Go to your settings page; open the account settings panel; scroll to the section for changing your Twitter-compatible service. Check the box “Reset to normal Twitter settings” and save changes.
This may fix your problem — there was an incorrect Twitter API URL in the old version which some users could have been using, and this should fix it. Let me know if it doesn’t, though!
Oh, I upgraded to 2.1.0 and I still get that message on all 3 of my blogs this morning (I use wordpress as a url shortener, btw). Do you think it’s just the Twitter API not being available at certain times?
Hi Joe - thanks for clearing that up - maybe a tiny to-do for the next version to make that message a little clearer - something like “If no categories are selected, then all categories will be tweeted” ?
I’ve noticed from my twitter tweet list ( http://twitter.com/GazLanNaThai ) that some of the posts were being tweeted twice yesterday - haven’t verified if this is related to the errors about not being able to tweet, as I forgot which posts delivered that message - is there a re-send attempt built into wp-to-twitter to cover for failed sends, or is it something WP_cron might pick up and activate?
Gaz
When all categories are deselected, there should be a note at the top of the section stating that ‘category restrictions are disabled’ (or something to that effect - I don’t remember the exact wording.) So, essentially, if you haven’t selected any categories to Tweet, the plugin assumes that all categories are approved for tweeting.
Glad you were able to restore everything!
Hi again - well that’s a big PHEW !!!
Looks like the hosts must have done the backup sometime in the hour or two between installing wp-to-twitter and the site disappearing, so no work lost and the first action was to update the plugin.
Now here’s a thing I thought of regarding the cli.gs failure messages after making a new post - in the wp-to-twitter settings page, the bottom section requires selection of the categories you want tweeted. I just noticed that none of my categories were selected - does this mean they are all not available to tweet, or does it mean they will all get tweeted using some sort of reverse logic?
What I’ve done for now is selected (ticked) all the categories except the uncategorised one. maybe the fact that they now have a mix of selection options will cause a difference in behaviour when posting - I’ll monitor it (this is an autoposting blog, so it’ll take a few hours) and report back. I’ll also try the same on one of my manual posting blogs and see if it makes a difference.
But first I need a couple of hours sleep - I ain’t seen my bed in the last 24 hours.
…. oh poo - have to install that backup plugin first, don’t I?
Gaz
Will do
I’m looking into several reasons behind this - it’s curious that the top level folder for the site (under public_html) was left in place, and it seems the database and email accounts etc are untouched - it’s only the entirety of the site files that are gone.
The hosts advertise a “weekly” backup is done as routine, so hopefully there’ll only be loss of some of the daily tweaks that were done after the site went into public beta, and I should be able to catch up quickly once they run a restore (waiting for their answer on this at the moment).
I must remember to install that WP backup plugin that zips and emails the site files and database nightly, and use it.
I’ve also spotted a flood of emails related to a line one failure in wp-rss.php / wp-rss2.php from the newsletter server that collected the feed for daily and weekly newsletter building - plus worryingly. it started trying to collect the feed every minute, which is not what the cron was set at (I checked it). I also remember reading on the WP forums something about an attack on the wp-rss files recently and last summer - wondering if it’s related? I recommend everyone use their hosting cpanel to look for malicious code in those files as it’s a known attack vector recorded by WP. Apparently there will be obfuscated code in there if you get hit.
Will update you once I know more.
Garry
That’s very unfortunate - I do feel for you. Let me know if you come back with anything concretely suggesting my plugin as the vector. I will definitely want to know.
Hi Joe - if you want to delete this after reading it, that’s OK, but it’s info you need to know.
Since my last post, WordPress are now offering the 2.1.0 upgrade in the admin panel - they were not when I posted …. 3 hours ago. So hoorah it’s got caught up.
However in that same time, the website linked to this post got hit so bad with something yet to be determined, that the host simply erased the entire site without warning - it completely locked their server. WP-to-twitter was the last plugin added, about 6 hours before they blatted the site, and right now, it is the prime suspect (for all the reasons discussed above).
This was a new build site that was only put live a fortnight ago, and was still being tweaked - and, yup, you guessed it - I had no backup of it, and the hosts didn’t take one before deleting it - that’s a solid month’s work gone Pfft.
I am very upset right now - the popularity of this site (from minute one) was huge, and it built a rapid following on facebook too. This was heading to be my best performing affiliate marketing site in my portfolio after just two weeks (it hit Google PR 3 and Alexa top 200K in that time). Now I have to rebuilt it again from scratch (I know I should have had backups, but I didn’t expect to need them this early - my bad).
I’m now off to kill wp-to-twitter on all the other sites until I can get to the bottom of this. Don’t discount your product being used as a vector by a competitor - such things do happen, and incidents like this are how they manifest to destroy confidence in your product.
Gaz
It’s not a backdoor; it’s a bug. Are you using 2.0.4 still, or have you upgraded? If this is still a problem in 2.1.0, let me know.
@dismal
Same here - it’s now affecting 7 sites, on 4 different hosting services, on two different continents - just haven’t had time to check all the other sites yet.
No idea if this is coming from cli.gs, or twitter, or the plugin, or the server, or what - too many variables involved - might have to install Pretty Links on all the blogs and use that to shorten then tweet manually (pain) until this is resolved.
Joe - not having a go at you, but this is getting widespread - has the latest version opened a backdoor and we’re all getting hit with something malicious affecting only the wp-to-twitter service?
I keep getting “There’s been an error posting your Twitter status! Visit your WP to Twitter settings page to get more information and to clear this error message.” - “One or more of your last posts has failed to send it’s status update to Twitter. Your Tweet has been saved in your post custom fields, and you can re-Tweet it at your leisure. Sorry! I couldn’t get in touch with the Twitter servers to post your new blog post. Your tweet has been stored in a custom field attached to the post, so you can Tweet it manually if you wish!”
Over and over again on 3 blogs I run, even on a fresh install of WordPress 2.9.2 with very few other plugins installed. And sometimes I get this message even when everything was posted correctly. Not really sure what’s happening.
Are you planninng to add support for OAuth?
This is question for the features rather then a problem…
But is there a way to tweet the the post to both the author and site’s twitter account?
Current i see no such option. If it’s possible please inform me. Thanks a million!
And this is a good Plugin!
Hi Joe
I got a strange issue arisen with wp-to-twitter. I’ve been using it for a few years on multiple sites without an issue, but something has definitely gone screwy since WP 2.9.x
As an example, one of my newer sites launched early this month (see the link I provided on this post) and was posting via RSS into facebook just fine. Then last Thursday (22 April) I added in wp-to-twitter sfter being sure everything else was stable.
Since then the RSS feed has not worked at all, and twitter shows a sudden flurry of tweets on the 22nd, then nothing. Crazy thing here is that there’s only 2-3 (maximum) posts per day on this site, so that’s all that should have appeared on the 22nd, but there’s a simultaneous batch of about a dozen - all within seconds of each other. The only thing that’s appeared since then is a post edit tweet while I was logged into the twitter site (open in a browser tab) while editing a post on the blog.
I’m going to try disabling wp-to-twitter to see if the RSS comes back on line (the facebook page for the site built a fanbase quite quickly, not as big as my twitter following, but healthy and more active in clicking through to the site).
For sending the tweets, right now it’s on the default non-subscription cli.gs service - I might switch it over to the WordPress post defaults shortener and see what happens, but the site name is longish, so not optimal.
Gaz
I am having the same problem as Bizzy (April 1, 2010)
I am using the newest version of the plugin (new installation), and it will post that I have made a new post on twitter - but it won’t include a URL. The Twitter post has the title of the blog post, the date, and the words “WP to Twitter”, but there is no URL. I am using Cli.gs as my URL shortener and have an API key.
Hosted on Justhost.com, WordPress Ver: 2.9.2
Thanks for following up, Alex! There are a lot of options to this plugin, so it’s actually pretty easy to get confused…
@Mark That’s a common problem — it has to do with the fact that most of the autoblog plugins skip the actions which WP to Twitter is attached to, feeding the data directly into the database or something similar. There’s nothing I can do about it, I’m afraid.
Hi
I think i have a bug when i am using wp to twitter and Article Fetch http://www.wparticlefetch.com/ when i have both activated wp to twitter do not post.
Is there a solution around this issue?
Many thanks
OK, let me be 100% clear here…
I AM AN IDIOT
Please ignore my previous posts, I now realise that I updated the categories on my website but failed to update the WP to Twitter options to tweet the new categories. @Joe, thanks for your support and apologies for my complete lack of skills. All is working fine now, thanks for a great plugin.
As already mentioned, there is a easy way to use the plugin with wordpress 3.0beta1 http://www.chrische.de/2010/04/wp-to-twitter-wordpress-plugin-unter-wp-3-0-beta1/
Hi @Joe,
That does help, I guess I was assuming that a when you publish a post previously saved as a draft that would be treated as a new post, not an update. It looks like all is working as intended, many thanks for your response.
Hi @Joe,
I was/am surprised that the plugin screwed up the theme as well. I deactivated and back to normal and then reactivated and its back to nothing in the sidebars.
If there is any other info you might need to help solve the prob, let me know. Thanks!
@Jakob Adding an author shortcode to the plugin is probably a good idea. I’ll put that on my list.
@Alex I’m not sure I fully understand your question — if you have the option selected to not tweet updates, then you won’t tweet updates — whether it’s a new post, draft, or any other form of publication. Does that answer your question?
@Jim Do you mean that the entirety of your sidebars are disappearing when WP to Twitter is activated? That’s extremely strange, since WP to Twitter should not have any effect at all on your theme.
@Anne Somebody is providing me with access to their server where this problem is being observed so that I can check on this; I’ll update when I know more.
Wordpress 2.9.2
Apache
New installation.
When I activate my plugin, the sidebars (both left and right) for my Amazing Grace theme do not show anything. Any ideas? Thanks, Jim
I’m having the same problems as Sal, Grendel and Radek - error message saying unable to shorten (“The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues. [Cli.gs Blog] [Bit.ly Blog]”), and the twitter output is not shortened, but bit.ly history shows the request was received by bit.ly and a short URL produced.
Currently using WP 2.9.2
Server is Apache
Problems seem to have started with the most recent version of WP, but I’m not certain.
Hi there,
Great plugin, I am far from an advanced user but this suits my needs. I have noticed that if you do not have the option selected to tweet updates then new posts that you either save as draft (or are autosaved?) are not tweeted. Is this correct?
Hello! A nice plugin, however we have one question or idea.
At the moment it looks like that shortcodes do not include #author# yet. Our wordpress installation has 4 artists, each of them is an author in wordpress, and so it would be good to be able to have tweets like #author# #title#…
Thanks for that suggestion, Byron — that’ll save me some time when I need to adjust the plugin for the version 3.0 release.
For WordPress 3.0b Users:
Add the following line above Line 48 in wp-to-twitter/functions.php
require_once ABSPATH.’/wp-includes/class-http.php’;
Awesome that worked, THANKS!
@Jacqueline It sounds like you’re using the short code for a text excerpt from your blog post.
It’s not trivial to filter non-HTML codes, so the best solution for you is to paste a text-only excerpt
into the blog excerpt field.
@Sal, Grendel, Radek I’ve heard very few comments to this effect, but it’s quite inconsistent; I’m not sure what might be going on.
@Robert No, there’s no option for comments to be updated. Maybe someday.
@Heather Yes, that’s possible; go to Account settings, check the box “Post status updates to both services” under “Change Twitter-compatible service”, and update your Twitter compatible service options. This will configure a second instance of Twitter as a secondary API, and send status updates to both instances.
WP Version 2.9.2
Server Type - Linux
Newish Installation
Is it possible to have WordPress send my posts to TWO different Twitter accounts? I only see room for one of my Twitter accounts, and I’d like to Tweet the same posts to two accounts.
Thanks.
Is it possible to have comments updated on twitter? I do not see a option for comments.
WP V 2.9.2
Serve Apache
New installation
Thats the plugin which I need but when I activate this plugin wp-admin/edit.php opens a blank page when I deactivate its turns to normal.
I have the same problem as Radek and Sal. I’m using bit.ly, the url shortening failed today and on March 3rd/6th, but I don’t see a pattern (and I never touch the config if everything works).
Same problem as Radek (March 30, 2010 at 3:53 pm) mentioned:
The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues. [Cli.gs Blog] [Bit.ly Blog]
But looking at bit.ly history, all recent URLs are there. It seems that the service is contacted, URL shortened, but the plugin does not get the response correctly.
Hi there, we just have one single problem: If pictures are includes in the blogpost, sometimes WPtoTwitter adds some code in the Twitter text.
f.e. Chace Crawford und die ‘Gossip Girl’-Crew singen Karaoke http://cli.gs/ZdJmv [ca #Chase_Crawford #Courtney_Love #Gossip_Girl #Taylor_Momsen
what does the [ca for ”caption” there?
Apart from that everythin is fine! Thanks for your support!
Cannot use object of type stdClass as array in /home/xxx/wp-content/plugins/wp-to-twitter/wp-to-twitter-manager.php on line 311
after this (??):
http://blog.bit.ly/post/519223659/bit-ly-1-3
longurl.org is down and that is breaking the plugin. Is there an option to not use longurl.org?
Im getting this one
Fatal error: Class ‘WP_Http’ not found in {MY_PATH}/wp-content/plugins/wp-to-twitter/functions.php on line 16
Maybe its the new 3.0 betas fault. Just wanted to g ive a heads up
Tough question. I am setting up a Classified website. Use you plugin on 2 other sites and love it. On this classified site however, the ads get “added” to page4 with an id so ?page_id=4&id=2 is ad 2 and so on. Is there aynway (maybe custom shortcodes?) to Tweet these new ads???
Thanks again for a great plugin Joe
Jim
That sounds like an interesting idea — I’ll look into it. I’m not sure how that will work, since it does require discovery of what custom post_types have been created, but it’s certainly an idea worth looking into.
Since WP 2.9+ supports more custom post_types, I would like to suggest adding support for these. Like posting type “post” in one way, and post type “review” in another way.
Also turning of automatic posting for given post types.
longurl.org appears to have disappeared. Are there any plans to use an alternate service for url expanding?
Greetings -
Thank you for creating this helpful plugin. When I create a blog post using the WP admin tool WP->Twitter tweets correctly (including the shortened URL from Cligs). But, our blog is also getting posted to via an XML feed (Brafton News Service w/plugin). These posts are not tweeting at all.
Found an error message within WP that said “I couldn’t get in touch with the twitter servers to post your new blog post”. I used the “Check Support” button which gave the all-good and a test post was tweeted. I’ve cleared the error and it has not returned. Any suggestions? Thanks in advance for any help you can offer.
Thanks,
Loren
WP 2.9.2
Apache (Media Temple Gridserver service)
New install (Brafton feed widget installed 1st, WP->Twitter 2nd)
Hi
Many thanks for a great plugin that has been very useful for me.
I’m wondering about an additional functionality and whether it would be possible to add it? I could probably hack the code to do it myself, but that would break future upgradeability, and would prefer that it’s built in to the core plugin.
Currently the system allows for a custom prefix for tweets according to whether it’s a new post or page, or a new edit and so on.
Would it be possible to build in a functionality for custom prefixes per top level post category?
So let’s say you had top level post cats of something like “Business, Classroom, Days Out” and so on - each of those can have their own tweet prefix, e.g. “New Biz Tip, New How To, Trip Report” and so on.
This would add more variety, interest, and relevance to the tweets, hopefully leading to more click-throughs to the actual posts.
Using a conditional such as -
if $cat_tree = (is_child_of($cat_ID) || is_category($cat_ID)) {
$tweet_prefix_ID = $tweet_prefix_text($cat_ID)
rest of code
}
I’m not a coder (just a copy and paste hacker) so that code would need worked on to get it right, but I hope you get the idea?
The main thing would be to have it dynamic enough to handle however many top level categories the blogger has set up (or might add or delete) and to offer the prefix input field in the admin panel. It could then save those to a database table with the categories relationships.
Another idea might be to offer WordPress default URLs as a short form for those without shortening service accounts - this could be done using the post/page ID in the form http://www.mydomain.tld/wordpress/?p=xxx. Alternatively, the Pretty Links plugin has its own build-in shortening engine (that also tracks clicks on the shortened URLs (both via a tracking pixel and using the HTTP_referrer classes to get the URL someone arrived from - it would be great to have something like this inside WP-to-Twitter.
Great work, but I’m a greedy so-and-so and want it all - LOL
Gaz
Hi,
I am using the newest version of the plugin - and it will post that I have made a new post on twitter - but it won’t include a URL. Anyone have any ideas?
Wordpress Ver: 2.9.2
It was an upgrade.
Hi there,
I’m WP 2.9.1 on Linux/Apache, and neither Cli.gs (with or without the API key) nor Bit.ly are working. This was a problem that started with the last version of the plugin. I upgraded to the most recent version but am still having a problem.
Any suggestions?
Sorry, here the needed informations:
WordPress 2.9.2
Apache/Linux Server
Version 2.0.2 - no upgrade
Thanks again.
Hi! First my thanks for WP -> Twitter. All in all it’s just the thing and works perfectly. There is just one little problem we have in our blog. We have mebers, that can’t publish by themself, but have to leave their drafts for reviewing. The editor or admin of the site is the one doing the publishing after reviewing. In this cases the new article is not announced on Twitter. In all other cases, WP -> Twitter works fine. Can you change this? Can I do it myself?
Many thanks in advance and keep up the good work!
All the best, Marius
Is there any way to disable the error messages?
According to the Bit.ly blog for March 30, 2010, it looks like they launched their new API … this might have broken something with the shortener. My test setup worked, first post worked .. now bit.ly doesn’t seem to work - have switched to wordpress ?= temporarily. If this plug in needs update for new API, please jump on that and I’ll kick in a donation
(I was waiting to see how well this works … I just switched it on today… on second post, hit the new API error!) doh.
I also have the following problem:
The query to the URL shortener API failed, and your URL was not shrunk. The full post URL was attached to your Tweet. Check with your URL shortening provider to see if there are any known issues. [Cli.gs Blog] [Bit.ly Blog]
But looking at bit.ly history, all recent URLs are there. It seems that the service is contacted, URL shortened, but the plugin does not get the response correctly.
Strange problem seems to be croping up - WP to Tweeter has started…lieing? i.e. Error reports that hasn’t been posted…yet…seconds later it is. Error reports that there was a problem with Cli.gs and/or Bit.ly and that the full url has been posted…but it has been posted with a shortened URL. This has just recently started happening - is this a problem with WP to Twitter’s upbringing or is something else going on?
I’m running…
WordPress 2.9.2.
Apache on Linux
Running current version of WP->tweeter
Problem listed above.
Exactly. Fortunately, ver. 1.5.7 works just fine…
Stopped working for me a few days ago. No idea why.
getting this error in wordpress 2.9.2: Fatal error: Cannot use object of type stdClass as array in /var/www/vhosts/XXX.XXXXXXX.XXX/httpdocs/wp-content/plugins/wp-to-twitter/wp-to-twitter-manager.php on line 308.
Thanks for a great plugin! Would it be possible for you to add the same options for categories as you currently have for tags (ie the ability to remove spaces etc)? I’m using the #category# shortcode for new posts at the moment, but would be extremely nice to be able to delete spaces or replace them with an underscore or similar when displaying the given category. Hope this can be implemented in an upcoming version - thanks again!
Hi,
Thank you for a great plugin! Worked perfectly until this update…
I updated to version 2.0.2 yesterday and since then the plugin sometimes works, and sometimes does not. The previous version worked flawlessly, and there were no account changes on either end.
When running the server support confirmation test (at bottom) it always returns a “successful” confirmation. However, sometimes the test transmits a test message to Twitter, and sometimes that message cannot be found (whether it is generated or not). Therefore, as a non-expert, my impression is that the transmission is unreliable.
Running on WP 2.9.2, Apache. Not sure what the previous version was, but I know I had ver. 1.5 running well before. (I don’t think I had intermediary upgrades, but it’s possible.)
Of course, I’d like it to work perfectly…
BUT, I don’t need to have the new category-limits feature (at least ‘new’ to me). If you don’t have a fix, is there any reason why I could not use ver. 1.5 going forward? As much as I’d like to be up to date, and compatible with the current WP version, I’d like the plugin to work - even more… 
Thank you for any suggestion you have!
MN
Hi,
I installed the WP to Twitter plugin on a WP Article Directory website and I have a problem. When I publish articles writed by the WP administrator everything is ok, but when I publish an article sent by an autor this are not sent to Twitter. Can you help me please?
Thanks
Cristian
Hey there, again… First update: It seems that the problem is caused by another plugin in my case. WP-to-Twitter is innocent, so feel free to ignore/delete/whatever my last comment
WordPress: 2.9.1
WP-to-Twitter: 2.0.2
Server: Apache 2, PHP 5.2.6
I’m currently trying to get my scheduled post problem under control. Up to now it was just “external_link” not being used. Now it seems that I also have the “nothing posted to twitter at all” problem.
I usually schedule my posts with Post Queue (http://www.andrewgrant.org/post-queue). In that case my posts got queued. Now I tried the “standard wordpress way”, but I don’t get any tweets, and I think I also have an explanation:
To debug my problems I added an extensive logging. Now I get an email with a list of all “do_action” calls for every page-call. Problem with scheduled posts seems to be, that neither “publish_post” nor “future_to_publish” is called.
This is a list of events fired during a “cron” call when a scheduled post was published:
Array
(
[…] startup
[26] => update_option
[27] => update_option_cron
[28] => updated_option
[29] => update_option
[30] => update_option_cron
[31] => updated_option
[…] irrelevant plugin
[36] => parse_query
[37] => pre_get_posts
[38] => posts_selection
[39] => loop_start
[40] => the_post
[41] => parse_query
[42] => pre_get_posts
[43] => posts_selection
[44] => loop_start
[45] => the_post
[46] => the_post
[47] => the_post
[48] => the_post
[49] => the_post
[50] => the_post
[51] => the_post
[52] => the_post
[53] => the_post
[54] => the_post
[55] => the_post
[56] => the_post
[57] => the_post
[58] => the_post
[59] => the_post
[60] => the_post
[61] => loop_end
[62] => shutdown
)
I think the post was published in steps 36-61.
I’m still digging into that problem and will keep you updated.
WP Version: 2.9.2
Server: DreamHost so not sure.
I completely removed the plugin and reinstalled/configured it. Did a new post this morning. The URL shortener works (using bit.ly) but every time is says if failed to contact Twitter.
I have checked and rechecked my twitter login creds with now luck. Am I doing something wrong?
Hello,
And thanks for this great plugin! It is by far my favourite Twitter related WP plugin.
One question. Would it be practicable to allow posting of blog comments to Twitter? For instance, when I approve a comment on my blog, post a link to it to Twitter (“New comment on post about apples and oranges: …”). This would be a great way to get Twitter followers in to a blog debate.
Or is that currently possible?
Thanks again!
Thanks, JohnB - somebody else had mentioned that there was an issue with the change from pending to published, and I’d forgotten about it - I’ll look at that as soon as I can.
Hi Joe,
Just installed this great-looking plugin. Am using it on a WordPress-based article directory. On it, article submitters post their article contributions, which we publish after due review.
The thing is that when i click on the “Publish” button after review, the posted doesnt get tweeted automatically, even though i have checked the “Update when a post is published” option under basic settings. To check whether the plugin is tweeting or not, I also checked the “Update when a post is edited” option and then “updated” the same post and voila! this time it got tweeted.
Now i don’t want to “publish” and then “update” every post to get it tweeted. Shouldnt the tweet go through when i publish a post? Is there a solution to this?
Thanks in advance.
It was a hosting related issue: http://twitter.com/cligs - they’re aware of it and it should be resolved soon.
There does appear to be an issue with Cli.gs today; but I’m afraid there’s nothing I can do about it. It doesn’t look like hacking; that looks more like a parking page. Perhaps there was confusion in the transfer of ownership, and Mr. Wong missed the boat on renewal; but I have absolutely no information.
@Michel There’s nothing that I’m aware of, sorry.
Hi,
cli.gs has gone offline today, all my tweets (around 140) are pointing to some parking page. I already switched the standard url shortener to bit.ly. Actually this is a twitter question, but do you know if it’s possible to remove all tweets and auto repost them again with a bit.ly short url?!
Michel
Hi,
does anybody else have problems with cli.gs???
All my shortened Urls are pointing to http://searchportal.information.com/
Even the cli.gs homepage points to http://searchportal.information.com/
Is it possible that they got hacked?!?!?
@Joe Dolson Oh wow. I kept totally overlooking that setting. I did have the box checked. Once I unchecked it, things were working as expected. Thanks so much.
Hi Joe,
Quick question. First of all thanks for all your work for this great plugin!
My works fine but my cligs URL’s always get repeated, first in quotes and then normally. I have the most recent version of your plugin and word press.
My twitter account is : halifax_realtor if you want to see what I’m experiencing.
Thanks,
Mike
@Dustin I think I know what’s going on. I’m going to take a stab at the idea that your settings are not actually the same between the two installations - one of them has the option “Post status updates to both services.” checked under the “Change Twitter-compatible service” section of the account settings. Checking that without changing to an alternate update service will give you two implementations of the Twitter API, with separate account information. If you haven’t filled out the second set of account settings., the plugin will attempt to post to both implementations, but will fail on one. Is that the problem?
@Guillermo I’ve never used Tweetdeck, so I can’t honestly say that I really know what you’re talking about. Sorry!
Hi Joe,
excellent plugin, I use tweetdeck and I don’t know how can i display my blog logo or photo. Every time I publish a post and send it to twitter using your plugin I got a empty box at tweetdeck instead of my logo or photo. Any suggestions?
Thanks very much.
@Joe Dolson Let me also clear up the fact, all my settings are savable. I’m 1st not understanding why I am seeing 2 different account setting boxes and 2nd why one errors and one doesn’t.
@Joe Dolson
Like I mentioned in my initial post, I use this WP Multiblog script that allows me to run multiple blogs off of one WP install. I couldn’t say if there is a conflict in that or not. If there was, I’d think it would affect both blogs the same.
I’d be more than happy to run any debug commands on the script that you think may help pinpoint what is occuring.
@Dustin But you’re unable to save the settings in the second installation? Strange. It’s entirely likely that the script you’re using to run two blogs on one set of files is causing some problem; but I’m not sure what it is. From the description of the script, it seems like this should work just fine - I’m not sure where there might be a conflict.
@JoeDolson Ah ha, well thanks. I’ll just sit around till WP 3.0 comes out and try again then. Thanks for all the help!
@Joe Dolson No they are two totally separate WP databases.
@Dustin Do the two blogs share a common database for options? Sharing the same files is irrelevant to the settings; but sharing the same database matters.
I’m still seeing the difference in the settings page when I run this plugin on my two blogs.
I have created an html page where you can see the results I’m getting. I must remind you that this plugin is ran from the same location on both blogs thus, I’d expect to see the same results.
http://blog.stelth2000inc.com/support/wptotwitter.html
I’ve gone about looking at how I have my php settings configured on my server and open_basedir is returning no value and safe mode is off.
Thanks for the assistance.
That combination of safe_mode with open_basedir is likely to cause problems with the
WP_httpclass. WordPress 3.0 is supposed to have a fix for this problem, but it’s out of my hands for now.Installed the update. Same error (WP to Twitter was unable to contact your selected URL shortening service.) I know my host runs under safe_mode with open_basedir in effect.
I’m just releasing an update, but I don’t know that it will fix all the problems here. I’ve been unable to reproduce the following issues:
1) Failure to contact url shortener services.
2) Scheduled tweets failing to use external links
3) Scheduled posts failing to post tweets.
4) Quotes in titles causing truncation of the tweet.
I’m aware that there’s a problem in WP 2.9.2 concerning http transports when the
open_basedirPHP setting is in effect; if those of you having these problems can check this, it may be worthwhile…although I have my doubts about it being relevant.WP: 2.9.2
Server Type: Apache
Installation: New
I am noticing something very interesting in regards to running this plugin. I currently have this plugin being shared with another blog I run, my personal blog @ http://blog.stelth2000inc.com using the following