Current version: 2.0.2
Donations to date: $361.00.
Downloads to date: ~128,200.
Donation per download: ~¼ cent.
2.0.0
- Fixed bug introduced in WordPress 2.9 where logged in users could only edit their own profiles and associated issues.
- Fixed bug which caused #URL# to repeatedly be added to the end of tweet texts on reactivation or upgrade.
- Fixed bug which generated shortener API error messages when no URL shortener was used.
- Fixed bug which prevented display of URL on edit screen if no URL shortener was used.
- Added Spanish translation courtesy of David Gil Pérez
- Made so many language changes that aforementioned translation is now terribly out of date, as are all others…
- Added ability to restrict posting to certain categories.
- Added option to dynamically generate Google Analytics campaign identifier by category, post title, author, or post id.
- Added option to configure plugin to use other services using the Twitter-compatible API.
- Added support for YOURLS installations as your URL shortener. (Either local or remote.)
- Redesigned administrative interface.
- Removed use of Snoopy and alternate HTTP request methods.
- Discontinued support for WordPress versions below version 2.7.
- Major revisions to support checks.
- Version jumped to 2.0.0
The WP-to-Twitter plugin posts a Twitter status update from your blog using the Cli.gs URL shortening service to provide a link back to your post from Twitter.
If you have a Cli.gs API key, the shortened URL will also be filed in your Cli.gs account so that you can track statistics for the shortened URL.
The plugin can send a default message for updating or editing posts or pages, but also allows you to write a custom Tweet for your post which says whatever you want. By default, the shortened URL from Cli.gs is appended to the end of your message, so you should keep that in mind when writing your custom Tweet.
Any status update you write which is longer than the available space will automatically be truncated by the plugin. This applies to both the default messages and to your custom messages.
This plugin is based loosely on the Twitter Updater plugin by Jonathan Dingman, which he adapted from a plugin by Victoria Chan. Other contributions by Thor Erik and Bill Berry.
Installation
- Upload the `wp-to-twitter` folder to your `/wp-content/plugins/` directory
- Activate the plugin using the `Plugins` menu in WordPress
- Go to Settings > WP->Twitter
- Adjust the WP->Twitter Options as you prefer them.
- Supply your Twitter username and login.
- Optional: Provide your Cli.gs API key ([available free from Cli.gs](http://cli.gs)), if you want to have statistics available for your URL.
- That’s it! You’re all set.
Comments on this post are now closed; please make support requests on the support page.
Version 1.4.2 has just been committed; I failed to include that file (required for PHP versions 5.1 and below) in the previous commit.
That’s what I get for hurrying to get a fix out!
Great Plugin! Works very well. Thx for developing it!
Hello!
Since I updated today, I get the error
Fatal error: Cannot redeclare class Services_JSON_Error in /srv/www/vhosts/manuel-rauber.de/httpdocs/wp-content/plugins/wp-to-twitter/json.class.php on line 797
when I try to activate the plugin.
Any Ideas?
Greetings from Germany
Hi
I am unable to activate your plug-in. I am running the latest WP
this is the message I get — thanks in advance!
Warning: main(/var/www/html/blog//var/www/html/blog/wp-content/plugins/wp-to-twitter/json.class.php): failed to open stream: No such file or directory in /var/www/html/blog/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 42
You must have downloaded the plugin during the interval between when I first uploaded 1.4.2 and when I noticed I’d made a typo…if you download the plugin again and over-write your existing copy, this problem should go away.
Sorry about that!
Thanks!!! funny, that. It works now.
Hiya
IM now also getting
Fatal error: Cannot redeclare class services_json in /var/www/vhosts/spiceworks-news.co.uk/httpdocs/wp-content/plugins/wp-to-twitter/json.class.php on line 116
As Manuel, any fix? i have redownloaded and tried to activate on another machine.
Great plugin though
Hi,
I downloaded it again (04.08.2009 8:33 UTC, 10:33 GMT+2), but the error is still present:
Fatal error: Cannot redeclare class Services_JSON in /srv/www/vhosts/manuel-rauber.de/httpdocs/wp-content/plugins/wp-to-twitter/json.class.php on line 116
Any ideas?
i am also getting the same json error. :\
AWESOME plugin. Just upgraded, got excited about being able to add my posts’ tags as hashtags. Then I realized, my half-asleep mind confused tags with categories — THAT would be nice. I tend to put tons of tags on my posts, but I keep the categories to a minimum.
In any event, I have my plugin set so that it ONLY tweets when new posts are published. However, when I updated a post, the plugin sent out a tweet that consisted of nothing but the tags from that post. So first of all, it shouldn’t have tweeted anything to begin with, since I have “post update” tweets disabled. Second of all, is it really just supposed to just “tag vomit” without the title or URL? Third, when there’s a multiple-word tag (I often tag names of people or companies mentioned in my posts), Twitter obviously only links the first word. Even though, as stated, I won’t be using the tag feature, others who do might find it nice if there was some way to convert the spaces to underscores and/or just eliminate them on the fly.
Found a bug with the new hashtag support, tags that contain spaces are handled very poorly, you need to either remove spaces or replace them with _
Just wanted to say a big thank you for this plugin. I’ve only just found it having waded through a large number of WP plugins that purported to post bit.ly or other shortening service links, only to find that they weren’t working properly and didn’t do the job I wanted them to, which is a shame - if they’re not ready for ‘prime time’ developers best serve themselves by holding back until they are. Yours works ‘straight out of the tin’, was a doddle to set up, and I’m very pleased with its ability to post Twitter notices not only of new blog entries but also edits, pages and blogroll links. Nicely done! Thanks again!
My WP to Twitter Settings page isnt loading anymore! =(
I just get an empty page.
I tried to reinstall the plugin but it didn’t help!
Any idea what could be wrong?
Thanks
This sounds like a great plugin. Will it post to more than one Twitter account?
Hi there, the plugin has started playing up for me was good up till just the other day. updated to 1.4.3. using wordpress 2.7.1.
You can see the problem here: http://twitter.com/bibigallery
I had the #tile# set but not the #URL# I was updating a post.
Same problem as @Melvin: the settings page is empty, after upgrading from 1.3
cheers,
Tom
@ Bruce: You can set an idividual Twitter Account for each WP-User-Account.
I’m running v.1.4.3 but don’t have these errors. It works pretty well for me.
The missing settings page is a known bug (in the FAQ) — did you attempt the solution provided above? If it didn’t work, then this is something new.
@cam There seems to be something quirky about updating posts in this version. Hopefully I’ll have time to fix that over the weekend.
It doesn’t work for me. Nothing happens!
No errors while installing?
Plugin activated?
Twitter Account added?
Ever since I upgraded I cannot use the plugin. I keep getting the following error:
Fatal error: Cannot use object of type stdClass as array in /html/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 272
Hi there,
I got the error message
I can’t delete it… Neither upgrading to the latest version..
Plus i would like to tweet the post if it was not tweeted.
Thanks
Is it possible to add code for post content, e.g. #content to insert first 100 characters from the post?
No, not at the moment. Given the demand, however, it will be one of the next features added.
Hi,
Can you allow us to remove the leadfing word “New:” please?
Don’t really need it, and it takes up a valuable 5 characters.
Thanks
@vince You can already do that. It’s in the settings.
Hi Joe,
Do you mean the text in the field “Text for this Twitter update” which by default has:
New: #title# (#URL#)
If so, when I remove the ‘New:’ my posts don’t get Tweeted
I can’t reproduce the error; what versions are you using?
I wondering if after deleting the word ‘New:’ it’s the leading # causing it
I am using WordPress MU 2.8.2 and your plugin version 1.3.7 as it works without issues otherwise and concerned about some of the new bugs others have reported.
I don’t provide official support for Wordpress MU, so I can’t say for sure whether it’s an issue with MU. I recommend giving version 1.4.4 a try — most of the bugs concerning 1.4 should be gone now, but this is something new to me, so I can’t say for sure whether it will be an issue.
-Joe
OK, went for the upgrade to your latest version, and can report back that everything works great. Excellent work, and thank you.
just wish I knew why I still get the RSS feed errors as an error log with tons of entries like this:
[10-Aug-2009 17:39:25] MagpieRSS: Failed to fetch (HTTP Error: malforme)
Using the FeedWordpress plugin
I had to go all the way back to 1.3.7 to have the plugin work.. even with 1.4.4 I still get the error: Cannot use object of type stdClass as array in /html/wp-content/plugins/wp-to-twitter/wp-to-twitter.php on line 272
Hi there, we have added wp to twitter, but when we want to post a message trough WP it does not show in twitter, does anyone know what the problem is?
Greetings erik
@Vince Glad that it’s working for you now. Wish I could help you with the FeedWordPress problem, but you’ll have to ask them!
@HotForWords I sent you an email with a patched copy, but I can easily imagine that you wouldn’t have received (unknown zip file from an unknown sender…) If you didn’t, let me know - I’d like to check whether the patch works before I make it public.
@Erik Have you checked to make sure all your settings are what you expect? Are you getting any error messages? Did you set your Twitter username and password?
Comments on this post are now closed; please follow comments on the new support page!