If you’ve got double titles when sharing your WordPress posts on Google+, it’s probably due to duplicate OpenGraph tags, which might have been caused by the latest update to Jetpack, which added OpenGraph tags in version 2.0. If you’re already running a plugin that outputs the “og:” tags in your document head, you’ll have to disable one or the other.
For example, to have WordPress SEO by Yoast not output the OpenGraph tags, go to SEO – Social and disable Facebook OpenGraph. If you’d like to disable Jetpack’s OpenGraph support, you’ll have to write some code, preferably in a plugin file:
add_filter( 'jetpack_enable_open_graph', '__return_false' );
Other plugins might be different, but you get the idea.
I always loved how commenting was over at WordPress.com, and the new Jetpack Comments brings all that fun stuff to WordPress.org blogs. Many of us have been waiting for this, and as announced by Tim Moore yesterday, Jetpack Comments are available as of version 1.4, along with some bug fixes. You should see an update available from your WordPress dashboard, and if you don’t, you can always download the newest version of the plugin from Jetpack.me.
I’m excited, thought it’ll probably take some time before I can use it here on my blog, because I hard-coded my comment form, instead of using the comment_form function. Bad, theme developer, bad! :)
Jetpack 1.3 has been released, and it now ships with the Grunion Contact Forms plugin, the very same forms plugin that’s running (behind the scenes) on WordPress.com. The update fixes a couple of small bugs as well. You should be able to download it from your Dashboard very soon.
It’s more difficult to keep this in mind, than it is to actually execute it. Sometimes we (content creators) want to publish content to see how it feeds to our Twitter or Facebook accounts, or to see how it turns up in the RSS feed, so what we usually do is publish a “test” post and delete it afterwards (together with the tweet and Facebook post.)
However, sent e-mails cannot be deleted, once they’re out there, there’s no turning back. It’s not the best user experience to receive a “testing my twitter plugin” e-mail, right? Jetpack is one of the best ways to deliver e-mail notifications, about your new posts, to your subscribers. I wrote about it before and actually use it myself.
The best way to prevent all of this is of course to use dummy accounts or staging servers. The second best way to test your posts publishing out, is to wait for actual content (and if things didn’t work, try again next time), but sometimes we want to just try it out in our live environment, and if you do that, don’t forget to disable Jetpack subscriptions, which can be done in two easy steps. In the Jetpack configuration page under Subscriptions, hit Learn More and you’ll see a Deactivate button.
Don’t worry, you will not loose all your subscribers, they’ll start receiving notification e-mails, when you Activate the subscriptions module again on that very same page, and yeah, don’t forget to activate it back when you’re done “testing things out.”
That’s about it! How do you handle test posts you don’t want your subscribers to see? Can you easily deactivate the e-mails with other plugins and services such as Feedburner? Share your thoughts and comments and thank you for subscribing!
I was thinking about this for quite some time now — an actual retweet button for WordPress, and I wonder why Twitter hasn’t provided one yet, it’s so obvious!
Yes, the tweet button is doing a great job these days, but let’s admit, that we content publishers enjoy retweets more than regular tweets to our articles, because:
- They show your name and your Twitter avatar along with the original message, so when others see your tweet retweeted, there’s a better chance they’ll follow you.
- They instantly show up in your Interactions and increase the retweet count, so you can always see who’s tweeting your posts, without having to use Twitter’s search.
- They give you a better chance to get a Top Tweet, thus providing even more exposure.
You can find a bunch of “subscribe to posts” plugins in the WordPress.org directory but from my personal experience, it’s very difficult to find something as good and reliable as Jetpack.
The major difference is behind the scenes — when most post subscription plugins will use the wp_mail function to distribute your new post (using sendmail from your server or an SMTP account,) Jetpack will simply send your new post to the WordPress.com server, which will take care of the distribution for you.