{"id":1398,"date":"2010-05-07T23:21:52","date_gmt":"2010-05-07T21:21:52","guid":{"rendered":"http:\/\/planetozh.com\/blog\/?p=1398"},"modified":"2010-05-08T01:06:57","modified_gmt":"2010-05-07T23:06:57","slug":"how-to-embed-a-tweet-in-wordpress-a-complete-oembed-tutorial","status":"publish","type":"post","link":"https:\/\/planetozh.com\/blog\/2010\/05\/how-to-embed-a-tweet-in-wordpress-a-complete-oembed-tutorial\/","title":{"rendered":"How to Embed a Tweet in WordPress: a Complete oEmbed Tutorial"},"content":{"rendered":"

A few days ago, Twitter published a new tool<\/a> that lets you embed a tweet on your site, simplifying the old school way: take a screenshot, crop the picture, upload it, embed it.<\/p>\n

The problem is: this Twitter tool is way too lame. Basically you need to cut and paste a lengthy code snippet full of HTML and CSS. How ugly. Compared to the way you can embed a Youtube video in WordPress (just pasting a video URL, on its own line) this is seriously cumbersome.<\/p>\n

Hey, wouldn't it be cool if you can embed a tweet just as easily? You would just paste its URL and let WordPress transforms it into a nicely presented tweet with links and everything? OK, let's do a plugin for this. And guess what, it's going to be fairly easy, using WordPress' oEmbed API implementation.<\/p>\n

\"\"
\n<\/p>\n

What is oEmbed<\/h2>\n

When you paste a Youtube video URL, raw (not hyperlinked) and on its own line, WordPress transforms it into an embedded video. Why? Basically, there's something in WordPress that says "every time you see a URL like http:\/\/www.youtube.com\/watch?v=*<\/tt>, ask http:\/\/www.youtube.com\/oembed<\/tt> what to do with it".<\/p>\n

In short, oEmbed<\/a> is a simple API that lets you define a URL pattern (used by a consumer<\/em>) and the URL of a script (the provider<\/em>) that will generate a clean HTLM out of it.<\/p>\n

Twitter does not support (yet) oEmbed, so we will have to handle this on our own: transform a WordPress blog into a oEmbed provider.<\/p>\n

Register your blog as an oEmbed provider<\/h2>\n

First, let's register our blog as an oEmbed provider, to replace all URLs like http:\/\/twitter.com\/ozh\/status\/13156561<\/tt> into a cool piece of HTML. If you can breathe and walk at the same time, you're qualified to do this: all we need is a single function call. The function to be used here is wp_oembed_add_provider( $pattern, $url_of_service)<\/tt>.<\/p>\n

\/\/ Return the internal URL that will handle the oEmbed requests (ie yourblog.com\/blog\/?ozh_tweet=1)\r\nfunction ozh_tweetembed_internal_oembed_url() {\r\n\treturn trailingslashit( home_url() ) . '?ozh_tweet=1';\r\n}\r\n\r\n\/\/ Register this internal URL as an oEmbed provider for twitter URLs\r\nfunction ozh_tweetembed_add_oembed_provider() {\r\n\t\/\/ http:\/\/twitter.com\/ozh\/statuses\/1234567\r\n\twp_oembed_add_provider( 'http:\/\/twitter.com\/*\/status\/*', ozh_tweetembed_internal_oembed_url() );\r\n}\r\nadd_action( 'init', 'ozh_tweetembed_add_oembed_provider' );<\/code><\/pre><\/div>\n
OK, so far, we're telling WP that everytime something looks like http:\/\/twitter.com\/*\/status\/*<\/tt>, it will have to ask yourblog.com\/blog\/?ozh_tweet=1<\/tt> what to do with it.<\/p>\n
Catch URLs that will contain ?ozh_tweet=1<\/h2>\n
Since we're now expecting WP to do something particular when called with ?ozh_tweet=1<\/tt>, we have to hijack this URL:<\/p>\n
\/\/ Register 'ozh_tweet' as a query var so we can check if ?ozh_tweet=1\r\nfunction ozh_tweetembed_add_tweet_query_var( $query_vars ) {\r\n\t$query_vars[] = 'ozh_tweet';\r\n\treturn $query_vars;\r\n}\r\nadd_filter('query_vars', 'ozh_tweetembed_add_tweet_query_var');\r\n\r\n\/\/ As early as possible, check for query var 'ozh_tweet' and maybe shortcut everything\r\nfunction ozh_tweetembed_get_tweet_query_var() {\r\n\t$tweet = get_query_var( 'ozh_tweet' );\r\n\tif( $tweet ) {\r\n\t\t\/\/ Make something with the oEmbed request\r\n\t\tozh_tweetembed_handle_oembed_request();\r\n\t\t\/\/ Now die, we don't want a blog page\r\n\t\tdie();\r\n\t}\r\n}\r\nadd_action( 'template_redirect', 'ozh_tweetembed_get_tweet_query_var' );<\/code><\/pre><\/div>\n
So, at this point, every time WP sees a line matching http:\/\/twitter.com\/*\/status\/*<\/tt>, it will ask yourblog.com\/blog\/?ozh_tweet=1&url=the_tweet_url&some_other_var=...<\/tt> what to do with it. So, what to do with it?<\/p>\n
Handling the oEmbed request itself<\/h2>\n
Now for the fun part: the function that handles the oEmbed request and return the expected formatted output.<\/p>\n
Basically, we're going to:<\/p>\n
    \n
  1. Guess the tweet id<\/li>\n
  2. Poll the Twitter API for information about this tweet, get a JSON response<\/li>\n
  3. Parse the JSON response, make something pretty with this it<\/li>\n
  4. Return that pretty thing into a JSON response<\/li>\n<\/ol>\n
    Vamos, muchachos:<\/p>\n
    \/\/ Handle the oEmbed requests\r\n\/\/ The oEmbed request is something like:\r\n\/\/ yourblog.com\/blog\/?ozh_tweet=1&url=http:\/\/twitter.com\/ozh\/statuses\/123456&...\r\n\/\/\r\nfunction ozh_tweetembed_handle_oembed_request() {\r\n\t$url = esc_url( $_GET['url'] );\r\n\tif( !$url )\r\n\t\tdie('URL missing');\r\n\t\r\n\tpreg_match( '!http:\/\/twitter.com\/([^\/]+)\/status\/(\\d+)!', $url, $matches );\r\n\t$author  = $matches[1];\r\n\t$tweetid = $matches[2];\r\n\tunset( $matches );\r\n\t\r\n\t\/\/ From this point, we fetch content from Twitter and print a JSON string.\r\n\t\/\/ If something goes wrong (like, Twitter unreachable) then we'll simply print anything but JSON\r\n\t\/\/ and let WP handle the response.\r\n\t\r\n\t\/\/ fetch http:\/\/api.twitter.com\/1\/statuses\/show\/$tweet.json\r\n\t$apiurl = 'http:\/\/api.twitter.com\/1\/statuses\/show\/'.$tweetid.'.json';\r\n\tif ( !$result = wp_remote_retrieve_body( wp_remote_get( $apiurl, array('timeout' => 15) ) ) )\r\n\t\tdie( "could not fetch $apiurl" );\r\n\r\n\t\/\/ Check that JSON is well formed\r\n\t$result = trim( $result );\r\n\tif ( !$data = json_decode($result) )\r\n\t\tdie( "Data was not JSON" );\r\n\t\r\n\t\/\/ Now extract a few variables from the $data object\r\n\t$text = $data->text;\r\n\t$created_at = date('d M Y g:i a', strtotime( $data->created_at ) );\r\n\tif( !empty($data->source) )\r\n\t\t$source = 'via '.$data->source;\r\n\tif( !empty($data->in_reply_to_screen_name) ) {\r\n\t\t$in_reply_to_screen_name = $data->in_reply_to_screen_name;\r\n\t\t$in_reply_to_status_id   = $data->in_reply_to_status_id;\r\n\t\t$inreply = "in reply to <a href='http:\/\/twitter.com\/$in_reply_to_screen_name\/status\/$in_reply_to_status_id'>@$in_reply_to_screen_name<\/a>";\r\n\t}\r\n\t$name = $data->user->name;\r\n\t$screen_name = $data->user->screen_name;\r\n\t$profile_image = $data->user->profile_image_url;\r\n\t\r\n\t\/\/ Make up some HTML with the tweet info\r\n\t$html = <<<HTML\r\n<div class="tweet">\r\n\t<div class="text">$text<\/div>\r\n\t<div class="meta">$created_at $source $inreply<\/div>\r\n\t<hr\/>\r\n\t<div class="pic"><a href="http:\/\/twitter.com\/$screen_name"><img src="$profile_image">$name<\/a><\/div>\r\n<\/div>\r\nHTML;\r\n\r\n\t\/\/ Put everything into a regular array\r\n\t$json = array(\r\n\t\t'version' => '1.0',\r\n\t\t'type'    => 'rich',\r\n\t\t'width'   => 1337, \/\/ this parameter is mandatory according to the oEmbed specs, but we're not using it\r\n\t\t'height'  => 1337, \/\/ same.\r\n\t\t'html'    => trim( $html ),\r\n\t);\r\n\t\r\n\t\/\/ Now output a JSON response\t\r\n\theader('Cache-Control: no-cache, must-revalidate');\r\n\theader('Expires: Mon, 26 Jul 1997 05:00:00 GMT');\r\n\theader('Content-type: application\/json');\r\n\theader('Content-Disposition: attachment; filename="oembed.json"');\r\n\techo json_encode( $json );\r\n}<\/code><\/pre><\/div>\n
    And… That's it. Now just paste a tweet URL and let WordPress do the job. For your convenience, get the whole plugin we've just dissected in a single file<\/p>\n
    \nDownload the plugin ozh-oembed-tweet.php.txt<\/a>
    \n(save as .php then put in your plugins folder)\n<\/div>\n
    Further improvements and remarks<\/h2>\n
    This simple "proof of concept" plugin returns very basic HTML, you'd need to make it prettier (use the tweet background, CSS style it). Just modify the "$html =" starting at line 44 or, even cooler, add an interface to the plugin where you can define a template for the tweet output. If you want some inspiration, I do something like this in my plugin Better Feed<\/a> where the user can customize feed item footer with a simple templating system.<\/p>\n
    When WordPress makes an oEmbed request, it does it once and stores its result in the postmeta table. Twitter has that feature we all know and don't care about any longer: unreliability. Notice the timeout parameter I've added to the remote request (line 21), this is really needed. Still, if you blog cannot fetch the tweet from Twitter's API, it will store a dummy postmeta entry ({{unknown}}<\/tt>) and won't replace the tweet URL. A proper plugin should test for the postmeta value and re-poll the Twitter API if applicable.<\/p>\n
    Twitter does not support oEmbed, but another site does it for them: Ooh Embed<\/a>. So, technically, a plugin to embed tweets using the oEmbed API would require just three lines, register oohembed.com as a producer. But that wouldn't be fun :) (and I don't know how reliable is oohembed.com)<\/p>\n
    Technically again, you could use more efficiently function wp_embed_register_handler()<\/tt> to deal with the oEmbed request without having to sending an extra HTTP request to your own site. But that would probably make a confusing example of the general mechanism of the API, with a consumer sending a request to a producer.<\/p>\n
    Any other comment or idea of something cool to do with Twitter and oEmbed? Use the comment form belllowwww<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"
    A few days ago, Twitter published a new tool that lets you embed a tweet on your site, simplifying the old school way: take a screenshot, crop the picture, upload it, embed it. The problem is: this Twitter tool is way too lame. Basically you need to cut and paste a lengthy code snippet full of HTML and CSS. How\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[367,371,85,292,245],"class_list":["post-1398","post","type-post","status-publish","format-standard","hentry","category-published","tag-how-to","tag-oembed","tag-plugins","tag-twitter","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/1398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/comments?post=1398"}],"version-history":[{"count":0,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/1398\/revisions"}],"wp:attachment":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/media?parent=1398"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/categories?post=1398"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/tags?post=1398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}