{"id":801,"date":"2009-02-11T00:49:33","date_gmt":"2009-02-10T22:49:33","guid":{"rendered":"http:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/?p=801"},"modified":"2010-08-24T10:52:32","modified_gmt":"2010-08-24T08:52:32","slug":"twitter-tools-patch","status":"publish","type":"post","link":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/2009\/02\/twitter-tools-patch\/","title":{"rendered":"Twitter Tools patch"},"content":{"rendered":"<p>Hi there!<\/p>\n<p>Lots of you may use <code>WordPress<\/code> as blog system. Lots of you may also use a <code>Twitter account<\/code>. I guess, most of\u00a0those people\u00a0will use the famous <code>Twitter Tools<\/code> plugin by Alex King (<a href=\"http:\/\/alexking.org\/\">http:\/\/alexking.org\/<\/a>) to automatically notify Twitter about your new WordPress blog posts.<\/p>\n<p><em>What happens while WordPress notifies Twitter?<\/em><\/p>\n<p>Well, the Plugin sends a notification to your Twitter account and, of course, tweets the URL of your new post. Since this URL is usually very long, Twitter uses (for some reason) tinyurl.com to shorten this URL. And this is, what I really hated. <strong>Really hated!<\/strong><\/p>\n<p>That&#8217;s the reason why I wrote the new <code>unfake.it-API<\/code>. Just as soon, as the API worked, I\u00a0wrote a <code>very tiny and very simple\u00a0WordPress plugin to enhance\u00a0Twitter Tools<\/code>. The plugin tells the Twitter Tools plugin to shorten URLs using my <code>unfake.it-API<\/code> before sending the URL of the new post to Twitter.<\/p>\n<p>The faked URL is short enough and Twitter doesn&#8217;t need to shorten it with tinyurl.com.<\/p>\n<p style=\"padding-left: 30px;\">Also see: <a href=\"http:\/\/unfake.it\/help.php#twitter-tools\">http:\/\/unfake.it\/help.php#twitter-tools<\/a><\/p>\n<p>So, all of you using WordPress and Twitter, you may (and should \ud83d\ude42 ) use this plugin.<\/p>\n<ol>\n<li><a href=\"http:\/\/www.thomasgericke.de\/tt_unfake_it.1.0.zip\">download the plugin here<\/a><\/li>\n<li>expand the archive into your <tt>wp-content\/plugins\/<\/tt> directory.<\/li>\n<li>create a folder named <tt>tt_unfake_it<\/tt> (should have happend automatically by unzipping the archive) in your <tt>wp-contents\/plugins\/<\/tt> directory.<\/li>\n<li>put the <tt>tt_unfake_it.php<\/tt> file into the <tt>wp-content\/plugins\/tt_unfake_it\/<\/tt> directory (should have happend automatically by unzipping the archive).<\/li>\n<li>go to the Plugins page in your WordPress Administration area and click &#8216;Activate&#8217; for &#8216;unfake.it URL shortener for Twitter Tools&#8217;.<\/li>\n<li>use WordPress as usual<\/li>\n<\/ol>\n<p><span style=\"font-family: verdana,arial,helvetica;\">Of course, <strong><code>you have to check<\/code><\/strong> <em>&#8220;Notify Twitter about this post?&#8221;<\/em> at the bottom of the editing page when writing a new post!<\/span><\/p>\n<p>That&#8217;s it \ud83d\ude42<\/p>\n<p>Once again: this is a plugin which depends on Twitter Tools by Alex King.<\/p>\n<p>Have fun and please let me know, if you&#8217;re experiencing any problems.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hi there! Lots of you may use WordPress as blog system. Lots of you may also use a Twitter account. I guess, most of\u00a0those people\u00a0will use the famous Twitter Tools plugin by Alex King (http:\/\/alexking.org\/) to automatically notify Twitter about your new WordPress blog posts. What happens while WordPress notifies Twitter? Well, the Plugin sends [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"ngg_post_thumbnail":0,"footnotes":""},"categories":[11],"tags":[51,61,151,141,111,1452,131],"class_list":["post-801","post","type-post","status-publish","format-standard","hentry","category-tech","tag-blog","tag-linux","tag-programming","tag-twitter","tag-unfake","tag-unfake-plugin","tag-wordpress"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/posts\/801","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/comments?post=801"}],"version-history":[{"count":6,"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/posts\/801\/revisions"}],"predecessor-version":[{"id":821,"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/posts\/801\/revisions\/821"}],"wp:attachment":[{"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/media?parent=801"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/categories?post=801"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thomasgericke.de\/v4\/interactive\/blog\/wp-json\/wp\/v2\/tags?post=801"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}