Sends status updates to Ping.fm or Twitter everytime you publish a post, using own domain or others for shortened permalinks.
Maybe, but use it at your own risk. I'll not support anyone using outdated WP (or outdated PHP). At the moment of writing this I’m running this plugin on WordPress 2.9 and PHP 5.x and works fine, and was running without problems on WP 2.8.x and 2.7.x too. If you run anything below WP 2.7 and PHP 5.x, please update for your own good! (and dont ask me for support).
I wanted a (single) simple plugin for using Ping.fm + Bit.ly to notify about new posts to my contacts.
At first only a few little improvements maybe. But if someone suggest a nice feature, and if I have time enough maybe I'll add it. But it's not my priority. I want to keep it simple.
<?php short_permalink(); ?> in your theme where you want to show short permalink. You can add the parameter 'linktext',
<?php short_permalink('linktext'); ?> and it will use the short permalink as text for the link too. Or if you have advanced knowledge of WordPress
theme coding, you can get the
'short_url' post meta directly and showing it as you like.
Twitter has decided to shorten ALL URLs (except the ones already shortened) sent to Twitter using Bit.ly service (without user API). But you can keep track of the statistics if you dont put your Bit.ly information in the Shorten2Ping settings.
From sometime ago Ping.fm has his own link shortener service too, so if you disabled Shorten2Ping option to make shorlinks, but you see http://ping.fm/xxxx when you notify a post through Ping.fm, you must disable this service in your Ping.fm account settings.
Since 1.3 version, Shorten2Ping adds a meta field in the single post view (the one that Facebook will scan) telling Facebook to use the first image uploaded and inserted in the post. If you want to override this, or simply you didn't uploaded any image to the post (even if you inserted one), you can add a custom field to the post named 'fb_img' and put the full URL to the image in the value for this custom field.
It only works with images that you uploaded to THAT post, so if you inserted an image from the media library that was uploaded previously to other post. You'll need to use the 'fb_img' custom field described before. I could add some code to sort this out, but the only way to make that (scanning the post content) could make the posting process slower if you use big images.