A new Open Source project has been launched today called Open Melody, which is a fork of Movable Type Open Source. Open Melody has been created by the MT developer community in order to take the product to the next level.

Why fork Movable Type? The Open Melody FAQs explain, "The community created Melody out a shared passion for Movable Type and a shared desire to see it flourish as a platform. We felt that the best and quickest way to achieve that goal was to create a product in which the community was inherently entrusted with a greater degree of control over its direction, communication channels and roadmap, and rewarded with more transparency and a greater sense of belonging."

In the spirit of being driven by the community, the current state of Open Melody is very similar to the latest version of MT. Going forward, features will be added and changes will be made in accordance with the community collaboration. So its too early to say what Melody will look like, and how it will be different from MT. Time will tell.

Why This is a Good Thing

Over two years ago, Six Apart, the creator of Movable Type open sourced the code for the core Movable Type application. While its was an exciting and bold move, the announcement and product naming choices were confusing to many -- the differences between Movable Type Open Source and the Movable Type Commercial product and closed source add-ons sold by Six Apart weren't easy to grasp, and some even disputed the newly open source nature of core application.

Bottom line is that the core of MT has been open source for 2 years, so what are the reasons and potential benefits of a separate branch of the application, why do we need Melody? In my opinion, the key benefit is that Melody will be developed completely by the community, with no direct ties to a commercial for-profit enterprise. While core MT has been open source licensed, the product planning process and much (but not all) of the discussion, prioritization, and release planning and scheduling were closed to those outside of Six Apart. Six Apart also acted as a gatekeeper to code contributions, with final say over what made into the final product. Both of these may be common for open source projects lead by commercial entities, and are fair enough -- Six Apart is a business and like any business they can and should make decisions based on the commercial interests of the company. But for the community of developers, consultants, and users, this didn't feel very open, at least in my opinion. The feature roadmap was being driven internally at Six Apart, not in a collaborative way with the community at large. [This is not to say that Six Apart did not listen to feature suggestions of the community -- many of the features added to the product were in response to community requests] The reality, I think, is that the internal business objectives that informed the development and product planning process are not fully aligned with the objectives of the broader community. This is an unavoidable reality, there is no right or wrong here, only different contexts and thus different perspectives and goals. For these reasons, I think many developers and end-users shied away from Movable Type -- despite the open source license, the product was controlled by a single for-profit company, and the ability of the external community to contribute and collaborate was limited.

Open Melody changes that dynamic. The core code becomes freed from the business concerns and objectives, thus enabling it to evolve in a way that is fully aligned with objectives and desires of the community. This means that roadmap planning, feature discussions, and development will all be completely open and collaborative. I hope that this will help attract more developers to the project and lead to faster release cycles and richer features that users want to see. With Open Melody, everyone wins: users, developers, community, the product, and even Movable Type and Six Apart. Its going to exciting to see how Melody evolves.

Current User of Movable Type?

If you are a current user of MT, you may be wondering what this means for you, should you switch when the time comes, or stay with MT? Today, there is a single, easy answer: wait and see. Melody is just getting started and it will probably be at least 6 months before a stable release is ready. So sit back and wtach how it evolves -- or better yet, contribute! Even if you are not a programmer, you can contribute by offering feature suggestions, etc. Another important thing to keep in mind is that a goal of Melody is to maintain compatibility with MT, so you should be able to switch back and forth, and use the same plugins and themes with either.

Melody and MT Hacks

I believe in the goals behind Melody and I hope it will be successful. I plan to contribute however I can, while at the same continuing to support the Movable Type platform. My goal is that plugins from MT Hacks will be supported on both platforms, which is aligned with Melody's objective of compatibility with MT. So if you use plugins by MT Hacks and you decide to move to Melody in future, you can continue to use the same plugins, and if you continue with MT, you can also keep using the same plugins. Of course, like any core MT upgrade, sometimes plugin updates are required, but those should work on both platforms.

Twitter Commenters is a plugin for Movable Type that enables commenters to sign-in and comment on your blog using their Twitter account. Versions 2 includes support for Twitter's OAuth authorization system and enables commenters to automatically share their comments to their Twitter stream.

Basic Auth (default):

OAuth:

Twitter comment authentication works like other auth methods in MT -- once you have installed the plugin you can enable Twitter as one of the auth options, as shown in the image above.

How It Works - Basic Auth

When the user enters their Twitter username and password in the form (shown above), the plugin submits those to the Twitter API to verfiy the credentials. If verified, the user can then post comments using their Twitter account. Their Twitter 'display name' will be shown beside their comments, and their Twitter avatar (profile photo) will be imported and shown beside their comments (if userpics are enabled in your templates).

Note that users' Twitter passwords are not stored in the MT database. An upcoming version of this plugin will enable Twitter's new OAuth support, in which case passwords would never be sent to MT at all. That version will like have an option for commenters to cc. their comments to their Twitter account. Stay tuned.

How It Works - OAuth

New in Version 2.0, you can optionally enable Twitter's new OAuth authorization system. With OAuth, user never have to submit their password info to your server. Instead, they click a "sign in with Twitter" button and they are taken to a page on Twitter.com asking them to authorize the application (see image above). One they click "Allow" they are returned to your site and they then post comments using their Twitter account. As with basic auth, their Twitter 'display name ' will be used as well as their Twitter avatar (profile photo).

Share Comments on Twitter

A new feature in version 2.0, only supported via OAuth, enables commenters to optionally share their comment to their Twitter stream. All they have to do is click a checkbox, no need to re-authorize or enter Twitter account info.

Try it Now

MT Hacks has the new OAuth method enabled. Try it now:

Click here to login with your Twitter account. After logging in, you will be returned to this entry, and you can leave a comment below.

Requirements

  • Net::Twitter 2.07 perl module (included with plugin) (note: do not upgrade to version 2.9+ of this module)
  • Net::Twitter::OAuth perl module (included with plugin)
  • Net::OAuth perl module (included with plugin)
  • Net::OAuth::Simple perl module (included with plugin)
  • JSON::Any perl (included with plugin)

Note: Net::Twitter requires newer versions of the libwww-perl collection of Perl modules. I am not sure what the minimum version required is, but on my server, I had to upgrade in order to get Net::Twitter to work. So if you get strange errors, try installing the latest version in your 'extlib' directory of your MT. Update: A common error message is: "Can't locate object method "default_header" via package "LWP::UserAgent" -- if you see this error, this the problem.

Download Twitter Commenters

Download Now
Downloads: 544

Installation

  1. Upload the contents of the 'plugins' folder to the 'plugins' directory for your MT install.
  2. Upload the contents of the 'mt-static' folder to your 'mt-static' directory.
  3. For each blog you want to enable, go to Preferences > Registration and check the box for 'Twitter'.

Enabling Twitter OAuth

Unfortunately, this is not as easy as it could be, maybe Twitter will make it easier in future. To set this up you need to create an Application on Twitter:

  1. While logged in to your Twitter account, go to http://twitter.com/oauth_clients/new.
  2. Fill out the form on that page:
    • Give it a unique name and description.
    • For 'Application Website', enter http://mt-hacks.com/twittercommenters.html. For 'Organization', enter MT Hacks.
    • For 'Website' enter http://mt-hacks.com.
    • For 'Application Type' choose 'Browser'.
    • For 'Callback URL' enter the full URL to your comments script followed by '?__mode=login_external&key=Twitter'. Example: http://www.domain.com/cgi-bin/mt/mt-comments.cgi?__mode=login_external&key=Twitter
    • For 'Default Access type' choose 'Read & Write'.
    • Check the box for 'Yes, use Twitter for login'
    • Hit the 'Save' button.
  3. After saving the application, you should now see a screen with a 'Consumer key' and 'Consumer secret'. Copy those to the system plugin Settings (System Overview > Plugins > Twitter Commenters > Settings). and save the plugin settings.
  4. To enable the share comment on Twitter option, add the <mt:TwitterShareCommentOption> tag below the comment text part of your comment form. This will display a checkbox option to people logged in via Twitter OAuth.
  5. Rebuild your entry pages and test it out

As always, feedback is appreciated.

Follow @mthacks on Twitter for updates and other MT and Twitter hacks.

Twitter Commenters is a plugin for Movable Type that enables commenters to sign-in and comment on your blog using their Twitter account.

Twitter comment authentication works like other auth methods in MT -- once you have installed the plugin you can enable Twitter as one of the auth options, as shown in the image above.

How It Works

When the user enters their Twitter username and password in the form (shown above), the plugin submits those to the Twitter API to verfiy the credentials. If verified, the user can then post comments using their Twitter account. Their Twitter 'display name' will be shown beside their comments, and their Twitter avatar (profile photo) will be imported and shown beside their comments (if userpics are enabled in your templates).

Note that users' Twitter passwords are not stored in the MT database. An upcoming version of this plugin will enable Twitter's new OAuth support, in which case passwords would never be sent to MT at all. That version will like have an option for commenters to cc. their comments to their Twitter account. Stay tuned.

Try it Now

Click here to login with your Twitter account. After logging in, you will be returned to this entry, and you can leave a comment below.

Requirements

  • Net::Twitter perl module (included with plugin)
  • JSON::Any perl (included with plugin)

Note: Net::Twitter requires newer versions of the libwww-perl collection of Perl modules. I am not sure what the minimum version required is, but on my server, I had to upgrade in order to get Net::Twitter to work. So if you get strange errors, try installing the latest version in your 'extlib' directory of your MT.

Download Twitter Commenters

Download Now
Downloads: 544

Installation

  1. Upload the contents of the 'plugins' folder to the 'plugins' directory for your MT install.
  2. Upload the contents of the 'mt-static' folder to your 'mt-static' directory.
  3. For each blog you want to enable, go to Preferences > Registration and check the box for 'Twitter'.

As always, feedback is appreciated.

Follow @mthacks on Twitter for updates and other MT and Twitter hacks.

Over at my Moopz site, I have just released a new Twitter Bookmarklet that make it easy to submit the link of the page you are reading. A pop up appears with a Twitter-like interface, enabling you to quickly tweet the page you are reading. It is designed to be clean and easy to use, a few seconds and you are done. The Twitter Bookmarklet looks like this:

Click here to head over to Moopz to get the Bookmarklet or to try it now.

During the past few weeks, there has been a lot of discussion about whether Twitter's "real time search" could pose a threat to Google.

While I am not sure if Twitter poses a threat to Google, I think it is clear that real-time search is increasingly important. And you can be sure that Google knows it. Will Google try to acquire Twitter, or take some other approach? Time will tell, but rather that wait, I decided to get realtime twitter search results on Google today. I created a Greasemonkey user script that does exactly this. It displays the most recent 5 tweets for the query that you are search for, giving both real-time Twitter search results and Google results on the same page:

I have been using it for a few days now and I think it really adds some freshness to Google search results pages. Not only do you get the web pages that have been indexed by Google, but also relevant twitter conversations that are happening right now. One day I think we may see Google release something like this, but until then there is the Twitter Search Results on Google Greasemonkey script.

Get realtime Twitter results on your Google searches:

  1. If you don't already have it, install the Greasemonkey add-on for Firefox.
  2. Click the "Install" button on the "Twitter Search Results on Google" page on userscripts.org.

If you like this, please tweet it by clicking here! (short url for this page is http://moopz.com/9ZDS)

Update: Also see my new Twitter Bookmarklet and Tweet This Page Link tool.

Feedback and suggestions are welcome, via comments on this entry, or via Twitter reply, FriendFeed, etc.

Selective Cloner is plugin for Movable Type that enables administrators to clone (copy) existing blogs. Unlike the blog cloning tool that comes with MT, Selective Cloner only clones Blog Settings, Permissions, and Templates. This plugin enables you to quickly create new blog with all of the same settings and templates as an existing blog -- in seconds you can have a new blog up and running, with the same look and feel. This is handy for blog networks or organizations who have more than one blog with the same templates.

Installation

Upload the contents of the 'plugins' directory to the 'plugins' directory of your MT install.
Go to "Manage Blogs" at the system level, click the checkbox beside the blog you want to clone, and choose "Clone Blog (Perms,Settings,Templates)".

License: GPL

Download Selective Cloner

Download Now
Downloads: 274

Pagination is plugin for Movable Type that enables you to paginate lists of entries. For example, at the bottom of your home page, you could add a "Next" link so your readers can go to "Page 2" and read previous entries. You can display a list of linked page numbers to enable visitors to jump to any page number they want.

With Pagination Pro, you can also paginate your Category, Author, and date-based archives, and even paginate your Entry archives, displaying only a small number of comments on each page. New in version 1.5: You can also paginate long entries by splitting them up into multiple pages.

New Features in Pagination 1.5

  • Support for MT 4.2 (minor bug fixes that may affect some sites running MT 4.2+)
  • New template tags for next / previous page numbers
  • Split long entries into multiple pages by easily inserting page breaks (Pro only)

Try it Now - Live Demo

The MT4 Test Blog has the Pagination Pro plugin enabled. Scroll to the bottom of the home page to see the list of pages and follow the links. Also take a look at an example of a paginated Category archive here. Finally, take a look at a paginated version of a 300+ comment entry here.

New: Paginated Entry Example - ReadWriteWeb

The latest version of the Pagination plugin is used by the popular technology blog ReadWriteWeb. (Disclosure: I provide consulting services to RWW) In additional, using Pagination to paginate the home page, category, and monthly archives, you can click here for an example of a long entry that has been split into 2 pages.

How it Works

My goal here was to create a pagination plugin with high performance. I didn't want it to slow down rebuilds, and I wanted pages to display for readers without delay. With these goals in mind, I decided to dynamically render pages 2, 3, 4, and so on. This means that unlike the default for most pages in Movable Type, pages 2+ are not static files that get published to your blog directories. They dynamically rendered by the plugin's page viewer script. Note that this viewer script is Perl-based and does not use MT's built-in PHP-based dynamic publishing system. The benefit of this is that you can virtually any plugin template tags in your paginated templates, and you don't need to use PHP. So when someone views page 2, the script goes into action and builds the page and displays it.

Paginated URLs are clean, ending in index.html?page=2 (or similar). Pagination makes use of mod_rewrite for Apache to keep these URLs clean (most MT sites run on Apache, but there may be some alternative approaches for other web servers).

Page-Level Caching

To speed up dynamic page views and reduce CPU/memory/database usage, Pagination supports (optional) page-level caching, powered by the Cache Block plugin. This means that once the plugins generates the HTML for "page 2", it will store that in the cache for next time. And next time someone wants to see "page 2", it can be quickly fetched from the cache. In my tests, dynamic page views from the cache took about 0.04 seconds, so this is very fast. In the plugin settings you can specify how long to cache pages before refreshing the cache.

Template Tags

Pagination comes with a template module that makes it easy to implement -- in most cases you can simply include the module in your existing templates and it will 'just work'. So you may not need to learn or use the template tags below. But if you want to customize the appearance of your Pagniation links, you can use/edit the following tags:

  • <mt:PaginationPages> - This is a container tag for displaying linked page numbers, previous / next page links, etc. This tag should only be placed inside the following containers: <mt:EntriesFooter>, <mt:EntriesHeader>, <mt:CommentsFooter>, and <mt:CommentsHeader>. There are several arguments:
    • max_pages - (Required) The maximum number of page numbers to display at one time. Note that page numbers will roll forward as readers view higher page numbers, just like Google paginated search results.
    • glue - (Optional) This should contain some text or symbols that you to display bewteen each page number. For example, if you want 1 - 2 - 3, then use glue=" - ".
    • lastn - (Required) The number of items shown on each page. This must match the lastn argument of the parent <mt:Entries> or <mt:PaginatedComments> tag.
    • archive_type - (Optional) For advanced use, you can use this tag to override the archive_type used to calculate the page numbers and links. If omitted, the plugin will use the archive_type of the page being built.
    • class_type - (Optional) For advanced use, this tag will override the type of MT object being counted to determine the number of pages.
  • <mt:PaginationPageNumber> - Used inside a <mt:PaginationPages> container, this tag will display the page number being processed in the loop (not the current page number that is being published/viewed).
  • <mt:PaginationPageLink> - Used inside a <mt:PaginationPages> container, this tag will display the URL to page number being processed in the loop.
  • <mt:IfPreviousPage> - Conditional tag that is true if the page being displayed is 2 or higher.
  • <mt:PaginationPreviousPageLink> - The URL to the previous page.
  • <mt:IfNextPage> - Conditional tag that is true if the currently viewed page is not the last page.
  • <mt:IfNotLastPage> - Conditional tag that is relative to the page being processed, not the page being viewed - returns true if the page being processed is not the final page.
  • <mt:LastPageLink> - The URL to the last page.
  • <mt:LastPageNumber> - The number of the last page.
  • <mt:NextPageNumber> - The number of the next page.
  • <mt:PreviousPageNumber> - The number of the previous page.
  • <mt:PaginatedComments> - (Pro only) This is replacement container tag for <mt:Comments>. If you want to paginate the list of comments on an Entry archive, you should use <mt:PaginatedComments> instead of <mt:Comments>. You can use all the same <mt:Comment_____> tags inside the container. Arguments include:
    • show - The number of comments to show per page. (Note that you can also use 'lastn' for this argument)
    • offset - The offset for the page of comments. This should always be set to "$pagination_offset".

Template Tags for Entry Pagination

A new feature in Pagination Pro enables you to split long entries into multiple pages by adding <!--nextpage--> (on a line by iteself) when writing the entry, in either the main "Body" or "Extended" fields. Then, using the following template tag modifer or tags, you display only the current "part" of the entry, along with pagination links. Note: in order to differentiate this type of pagination, the term "part" is used instead of "page" -- think of it as splitting an entry into multiple parts.

(Note that using <!--nextpage--> for page breaks is consistent with the built-in feature of Wordpress. This consistency may come in handy for sites migrating from WP to MT, as the existing page breaks should "just work".)

The easy way to use this feature is to use a new modifier called paginate on the tag that you want to split into parts for example:

<mt:EntryBody paginate="1">

or

<mt:EntryMore paginate="1"> (if your page breaks are added to the "Extended" field)

Simply add the paginate="1" argument to your existing tags in your Entry archives and MT will display only the relevant part of the field, along with pagination links at the bottom.

If you want more flexibility, instead of using the modifier described above, you can use the following template tags to control the display of the parts and page numbers:

  • <mt:PaginatedTag> - This container is designed to container the part(s) and page links for a paginated Entry Field. There is one required argument:
    • tag - The tag with the page breaks, without the "mt:" prefix. Valid values are 'EntryBody' and 'EntryMore'. Example: <mt:PaginatedTag tag="EntryBody">
  • <mt:CurrentPart> - This tag displays the current part of the tag (part 1 on page 1, part 2 on page 2, etc.). This tag must be used inside a <mt:PaginatedTag> container.
  • <mt:Parts> - This container tag list the pages and page links for each part, if page breaks exist in the specified tag. This tag must be used inside an <mt:PaginatedTag> container. There is one optional argument:
    • glue - the value of glue will act as a separator between each part number. Example: <mt:Parts glue=" | ">
  • <mt:PartNumber> - Displays the part number.
  • <mt:PartLink> - Displays the URL that links to page for the part.
  • <mt:IfPreviousPart> - Conditional tag that is true if the part being displayed is 2 or higher.
  • <mt:PreviousPartLink> - The URL to the previous part.
  • <mt:IfNextPart> - Conditional tag that is true if the currently viewed part is not the last part.
  • <mt:NextPartLink> - The URL to the next part.

Variables: For advanced usage, several variables are set by the plugin. A global variable called 'current_part_number' will be assigned to the value of currently displayed part on pages 2+, but remains undefined on page 1. Within an <mt:Parts> container, a local variable called 'current_part' is assigned to a value of 1 if the part being processed is the currently displayed part. Finally, standard loop variables such as __first__, __last__, etc. are assigned and can be used inside <mt:Parts>

Complete Example:

<mt:PaginatedTag tag="EntryMore">

<mt:CurrentPart>

<mt:Parts glue=" &nbsp;">
<mt:If name="__first__">
<div class="partination"><p><strong>Page: &nbsp;
<mt:IfPreviousPart>
<a href="<mt:PreviousPartLink>">&laquo;&nbsp; Prev</a>
</mt:IfPreviousPart>
</mt:If>
<mt:If name="current_part">
<mt:PartNumber>
<mt:Else>
<a href="<mt:PartURL>"><mt:PartNumber></a>
</mt:If>
<mt:If name="__last__">
<mt:IfNextPart>
<a href="<mt:NextPartLink>">&nbsp;Next &nbsp;&raquo;</a>
</mt:IfNextPart>
</strong></p></div>
</mt:If>
</mt:Parts>

</mt:PaginatedTag>

Note: the template tags above will only work on templates published using MT's default "static" publishing system. The tags will generate an error if used on dynamically published templates.

Templates Set

Pagination comes with two templates:

  • Pagination - A template module that can be included in other templates to display page links.
  • HTACCESS for Pagination - An index template that builds the required mod_rewrite rules. Important: The output file for this template has been set to "htaccess.txt" on purpose. Some sites have already have a ".htaccess" file and you want to be careful not to overwrite the existing one (for example, if you use MT's PHP dynamic publishing, with my Fast Search plugin or otherwise). Check to see if you already have an .htaccess file and if you do, you may want build this template as "htaccess.txt" and then copy and paste the rules into the appropriate place in your .htaccess file (if using MT's dynamic publishing, paste before the existing rules.) If you want to use this template to build your .htaccess file, you will need to change the output file to ".htaccess".

Requirements

Note: while not required, the Cache Block plugin is needed if you want to use the Pagination caching features (highly recommended).

Installation

  1. Download the zip file and upload the contents of the 'plugins' folder to the 'plugins' directory of your MT installation.
  2. Change the permissions of the /plugins/Pagination/pages.cgi script to 755 (CHMOD 755).
  3. Go to the blog you want and then to Preferences > Plugins and then open the settings for the Pagination plugin. Enable the caching settings if desired, then Save.
  4. Return to the settings and click the "Install Templates" button. This will install the templates mentioned above.
  5. Setup your .htaccess file with the Pagination rules, as described above.
  6. Edit your Main Index template and add the following before the </MTEntries> tag:

    <mt:EntriesFooter>
    <mt:Include module="Pagination">
    </mt:EntriesFooter>

  7. Modify your <MTEntries tag to include the argument offset="$pagination_offset". This is important. Example: <MTEntries lastn="10" offset="$pagination_offset">

  8. (Pro only) Do the same for your "Entry Listing" archive template, for both MTEntries containers.

  9. (Pro only) If you want to paginate your comment listings on your Entry archives, edit the "Comments" template module to replace the <MTComments> container with the MTPaginatedComments container, as discussed above. Be sure to include show="10 offset="$pagination_offset".

  10. (Pro only) If you want to paginate long entries on your Entry archives, edit your Entry archive (or relevant template module) to replace or modify the EntryBody or EntryMore tags, as described above.

Get Pagination Pro

Commercial License for 1 to 10 blogs - $97

Blog Network License for 10+ blogs - $249

Personal License for 1 to 4 blogs - $33

Get Pagination

Pagination is free for personal or commercial use, but you must leave the "powered by" link, which is added automatically below the paginations links.

Download Now

Download Now
Downloads: 1558

Membership required, please sign-in or register:

As always, comments, questions, and suggestions are welcome.

FriendFeed Comments is a plugin for Movable Type that enables you to import and display comments made using FriendFeed on your entries. You can also use the plugin to enable your blog commenter to "Cc." their comments to FriendFeed (if they have a FriendFeed account).

Background: FriendFeed Comments

FriendFeed is service that enables you aggregate and share your stuff from many other web sites, all in one place. Your feed can pull in your blog RSS feeds, photos from Flickr, videos from YouTube, tweets from Twitter, and many more.

Each item in your feed -- whether it is a blog entry or tweet -- can be commented on by other FriendFeed users.

Some great discussions about blog entries can happen on FriendFeed. The only problem is that those conversations are off-site and separated from the entry published on your blog. One of the goals of the FriendFeed Comments plugin is to bring those comments back to your published blog entry, displaying them with on-site blog comments.

Features

Version 1.0 of the FriendFeed Comments plugins includes the following features:

  • Checks all types of FriendFeed items for comments on your entries. Usually, comments on FriendFeed happen on the RSS item from your entry. Some comments, however, happen on the Twitter message you posted to announce the entry. The plugin aggregates these all these comments by checking all items in the feed.
  • Imports the comments as real MT comments. After importing, comments appear in the admin area just like other comments. Comments are displayed interspersed with on-site comments, displayed in chronological order.
  • New template tags can be used to highlight FriendFeed comments (more info below)
  • High perfomance, does not slow publishing. FriendFeed comments are imported via an MT scheduled task, running every 15 minutes in the background.
  • Check multiple FriendFeed user's feeds for comments. Useful for multi-author blogs and other advanced uses.
  • On-blog commenters can optionally Cc. their comments to FriendFeed. In addition to posting the comment on your blog, the comment will also be posted to item in your FriendFeed. Also, the comment will be posted as an item in the commenter's feed, so they can share the comment (and link) with followers of their feed.

Working Example: ReadWriteWeb

This plugin was suggested by Richard McManus and Marshall Kirkpatrick of ReadWriteWeb, and inspired by the FriendFeed Comments plugin for Wordpress, by Glenn Slaven. I have installed the plugin for ReadWriteWeb and it is now running, importing comments from FriendFeed and enabling commenter to Cc. FriendFeed. Check out the entries at http://www.readwriteweb.com/. Please don't post "test" comments there, you can use the live demo for that...

Live Demo

If you have a FriendFeed account, you can try out the plugin right now:

Click here to access the live demo for FriendFeed Comments.

Requirements

  • MT4+
  • JSON 2.x Perl module (included)
  • Net::FriendFeed Perl module (included)
  • Remote Comments Schema plugin (included)

Get FriendFeed Comments

This plugin is free to members of MT Hacks.

Download Now

Download Now
Downloads: 156

Membership required, please sign-in or register:

Installation

  1. Download and expand the zip file.
  2. Upload the contents of the 'plugins' folder to the 'plugins' directory of your MT.
  3. Upload the contents of the 'extlib' folder to the 'extlib' directory of your MT.
  4. Upload the contents of the 'mt-static' folder to the 'mt-static' directory of your MT.
  5. Login to MT and go to the blog you want. Go to Tools > Plugins and choose FriendFeed Comments and then Settings. Enter the FriendFeed username(s) of the feed(s) that contain links to your blog entries. Save the settings.
  6. Ensure that scheduled tasks are running, ideally via cron job. Click here for more info. Comments will only be imported if scheduled tasks are running.
  7. (Optional) Modify your templates using the new template tags described below. If you are using the new MT4-style templates, you probably want to edit the "Comment Detail" template module.
  8. (Optional) Modify your comment form to enable on-site commenters to Cc. their comments to FriendFeed. You need to add two fields named friendfeed_user and friendfeed_remote_key. If you want to use the code shown on the demo entry, you can download this template module and include it.

Template Tags

FriendFeed Comments adds the following new template tags:

  • <MTIfFriendFeedComment> - A conditional tag that is true if the comment exists on FriendFeed.
  • <MTIfFriendFeedEntry> - A conditional tag that is true if the entry in context has been found on FriendFeed.
  • <MTFriendFeedEntryLink> - A URL to the item for the entry on FriendFeed.
  • <MTFriendFeedIconURL> - A URL to the small FriendFeed icon.

Example usage, place before the commenter's name:

<MTIfFriendFeedComment><a href="<MTFriendFeedEntryLink>" target="_blank" title="Posted on FriendFeed">
<img src="<MTFriendFeedIconURL>" align="left" alt="Posted on FriendFeed" /></a>  </MTIfFriendFeedComment>

As always, feedback is welcome.

Remote Comments Schema is plugin for Movable Type developers. The plugin is very simple and provides no new "features". As the name suggests, the plugin provides a database schema for remote comments. Specifically, this plugin extended the MT::Comment object by adding two new (real, not meta) columns:

  • remote_service
  • remote_id

These fields can be used to link MT comments to comments stored/created/imported/synced on remote service.

License: GPL

Download Remote Comments Schema

Download Now
Downloads: 112

A new version of the Fast Search plugin for Movable Type is available.

The new version is a very important security update, and I recommend that all sites install the new version as soon as possible.

The primary issue that has been fixed was a security bug in which a malicious person could insert HTML or javascript into your search results pages by modifying the query string. Please note that this does not affect regular user searches or tag searches, but rather search results pages that spammers have linked to from external web sites.

Other fixes include a pagination issue that was affecting certain users (in which the page numbers were inaccurate), and a fix for the tag_dir argument when the blog was not at the root off the domain.

You can download the new version from the links below:

Download Now

Fast Search 2.22 for MT4+:
Download Now
Downloads: 4725 (since 3/6/07)

Fast Search 2.092 for MT3.2 and 3.3:
Download Now
Downloads: 4725 (since 3/6/07)

If you have previously purchased the Pro version, you should have by now received an email with a download link. If not, please contact me.