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: 1620

Membership required, please sign-in or register:

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

Entry To Page Converter is a plugin for Movable Type 4 that enables you to convert Entries into Pages.

Pages are a new feature in MT4 that you can use to create pages that are not really 'entries'. In previous versions of Movable Type, many people used entries for such pages. Now that MT4 has "pages", you can use this plugin to easily convert those old entries into pages. By the way, you can also do the reverse, convert Pages into Entries.

How it Works

On the Entry listing screen, you can select the entries that you want to convert by checking the boxes. Then simply choose "Convert to Page(s)" from the "more actions..." dropdown menu and click "Go". The Entries will immediately be converted to Pages. During the conversion process, the entry is automatically removed from any categories it may have been in, since Pages don't use categories. After the conversion process, you will be redirected to a "Batch Edit" screen for your new pages. Using this screen, you can quickly add Pages to Folders and other minor edits, then hit save. It's that easy.

Requirements

  • MT4.0+

Installation

  1. Download and extract the zip file, then upload the contents of the 'plugins' directory into the 'plugins' directory of your Movable Type installation (often /cgi-bin/mt/plugins/).
  2. Login to MT and go to the entry listing for the blog you want.
  3. Select the entries that you want to convert by checking the checkboxes.
  4. Choose "Convert to Page(s)" more the "more actions..." dropdown box and click "Go"
  5. (Optional) Add the new pages to Folders and make other edits, then save.
  6. Rebuild your site.

Get Entry to Page Converter

Commercial License - $25

Visitor Stats is free for non-commercial use, to members of MT Hacks.

Download Now

Download Now
Downloads: 224

Membership required, please sign-in or register:

Comments and Suggestions are welcome, please post a comment.

Download Now

FormatList v1.4

Membership required, please sign-in or register:

This is a minor update to FormatList that provides no new functionality. Version 1.4 includes updated button images ( and ) that match the new buttons in Movable Type 3.31. (Thank you to demonsurfer for help with these images!)

Requirements: Movable Type 3.3 or higher

For more information about FormatList, click here.

Previous versions of FormatList will not work with Movable Type 3.3 (or later). The new version (1.2) will only work with MT 3.3 or later.

FormatList no longer requires the BigPAPI plugin.

Download Now

FormatListv1.2.zip

Membership required, please sign-in or register:

If you want to use FormatList with MT 3.2, please download:

FormatList1.1forMT3.2.zip

Membership required, please sign-in or register:

FormatList adds list buttons to the toolbar, in the MT admin entry screens. For more information, click here.

Note: with this version, I have not updated the button images to reflect the new sizes that are used by MT 3.3, so you may notice a slight difference in size, compared to the new 3.3 toolbar buttons.

New in version 1.1: I fixed a bug that was preventing the list buttons from working in the "Extended Entry" field. The features remain the same, as described below.

FormatList is a plugin for Movable Type that makes it easy to create bulleted or numbered lists when creating or editing entries.

FormatList adds the following two button to the formatting toolbar that appears just above the "Entry Body" and "Extended Entry" fields:

To create a bulleted list:

  • Enter the list of items, hitting enter after each line (you can leave blank lines in between list items if desired)
  • Select (highlight) the list
  • Click the button

To create a numbered list:

  1. Enter the list of items, hitting enter after each line (you can leave blank lines in between list items if desired)
  2. Select (highlight) the list
  3. Click the button

Requirements:

  • BigPAPI Plugin (For convenience, I have included this plugin in the FormatList download) (more about BigPAPI)
  • Movable Type 3.16 and higher (I think....currently tested with MT 3.2 only)

Download Now

New in version 1.1: I fixed a bug that was preventing the list buttons from working in the "Extended Entry" field. The features remain the same, as described below.

FormatList is a plugin for Movable Type that makes it easy to create bulleted or numbered lists when creating or editing entries.

FormatList adds the following two button to the formatting toolbar that appears just above the "Entry Body" and "Extended Entry" fields:

To create a bulleted list:

  • Enter the list of items, hitting enter after each line (you can leave blank lines in between list items if desired)
  • Select (highlight) the list
  • Click the button

To create a numbered list:

  1. Enter the list of items, hitting enter after each line (you can leave blank lines in between list items if desired)
  2. Select (highlight) the list
  3. Click the button

Requirements:

  • BigPAPI Plugin (For convenience, I have included this plugin in the FormatList download) (more about BigPAPI)
  • Movable Type 3.16 and higher (I think....currently tested with MT 3.2 only)

Download Now

FormatList.zip

Installation Instructions:

  1. Download and expand the zip file
  2. Upload the contents of the 'plugins' folder to the 'plugins' folder of you MT installation (there are two files, FormatList.pl and BigPAPI.pl)
  3. Upload the contents of the' images' folder to the 'images' folder within the 'mt-static' folder. This is the location of the images and docs for MT, for most people it will likely be in '/mt-static/images' (outside your cgi-bin).

I hope others find this as helpful as I do. I created this plugin becuase it was quite tedious to create list manually, and this plugin makes it really quick and easy.

Note: As you would expect, each of the lists above was created using FormatList ;)

FormatList is a plugin for Movable Type that makes it easy to create bulleted or numbered lists when creating or editing entries.

FormatList adds the following two button to the formatting toolbar that appears just above the "Entry Body" and "Extended Entry" fields:

To create a bulleted list:

  • Enter the list of items, hitting enter after each line (you can leave blank lines in between list items if desired)
  • Select (highlight) the list
  • Click the button

To create a numbered list:

  1. Enter the list of items, hitting enter after each line (you can leave blank lines in between list items if desired)
  2. Select (highlight) the list
  3. Click the button

Requirements:

  • BigPAPI Plugin (For convenience, I have included this plugin in the FormatList download) (more about BigPAPI)
  • Movable Type 3.16 and higher (I think....currently tested with MT 3.2 only)

Download Now

FormatList.zip

Membership required, please sign-in or register:

Installation Instructions:

  1. Download and expand the zip file
  2. Upload the contents of the 'plugins' folder to the 'plugins' folder of you MT installation (there are two files, FormatList.pl and BigPAPI.pl)
  3. Upload the contents of the' images' folder to the 'images' folder within the 'mt-static' folder. This is the location of the images and docs for MT, for most people it will likely be in '/mt-static/images' (outside your cgi-bin).

I hope others find this as helpful as I do. I created this plugin becuase it was quite tedious to create list manually, and this plugin makes it really quick and easy.

Note: As you would expect, each of the lists above was created using FormatList ;)

For a complete list of the new features in v0.6, click here.

MTTrackbackEntry is a Movable Type plugin and hack that enables you to create new entries from the Trackbacks that you receive. In other words, it enables other people to post new entries in your blog, simply by pinging an entry or category on your blog. The title of this plugin/hack could just as easily be called TrackbackCrosspost, since it can act as a trackback-based cross-posting tool.

Currently, entries are created AND pings are received and recorded by default. In v0.6, actual ping entries can be optionally turned off. So if you turn off pings, TrackbackEntry will only record a new entry. Personally, I can't think of many practical cases for record the ping as well - it just clutters up your database.

TrackbackEntry is especially useful when used to ping Categories rather than entries. When a category is pinged, the new entry is added to that category. This provides more control over the display of Trackback-Entries (display in sidebar, sub-page, etc.)

New: Category Creation

In v0.6, you can enable a new category creation feature. This powerful feature enables people to create entries in categories that don't yet exist on your blog. For example, ping the following:

...mt-tbentry.cgi/books

would create a new category in your blog called "books" and add the entry to that category. If your blog already has a category called "books", the entry is simply added to that category. One of the benefits of this approach is that people don't need to remember the trackback id of the category.

MT-Blacklist Support

Version 0.6 includes optional support for MT-Blacklist. I have only tested this with v 1.63rc2 with MT 2.661. When this option is turned on, incoming pings are scanned against your blacklist just like a real trackback. This option is off by default.

Template Tags

There are only two new tags provided (because most of functionality lies in the scripts, not in the plugin itself). The following tags enable you to output the TrackbackEntry URLs for entries and categories:

<MTEntryTrackbackEntryLink> - Similar to <MTEntryTrackbackLink>, this tag will display the TrackbackEntry URL for a particular entry. Others can use this URL to to send a TrackbackEntry ping, which will create a Trackback record for the entry and create a new entry in the blog.

<MTCategoryTrackbackEntryLink> - Similar to <MTCategoryTrackbackLink>, this tag will display the TrackbackEntry URL for a particular category. Others can use this URL to to send a TrackbackEntry ping, which will create a Trackback record for the category and create a new entry in the category.

Requirements

Net::Blogger - Sorry, I neglected to mention this is the first release.

Installation

1. Download Now:

MTTrackbackEntry.zip and extract the files.

Membership required, please sign-in or register:

2. Place "mt-tbentry.cgi" in your MT directory (same directory as mt.cgi). Then CHMOD to 755.

3. Place "TrackbackEntry.pl" in your "plugins" directory within your MT directory.

4. Create a new user to be be used for Trackback-Entries. Make note of the username and password. Give the user permisions to post and rebuild files on each of the blogs that you want to enable TrackbackEntry.

5. Open "TrackbackEntry.pm" and find the line that reads:

my $mt_username = 'tbentriesusername';

Replace 'tbentriesusername' with the user name chosen in Step 4 (the username should be enclosed in single quotes). (remember that MT usernames are case-sensitive)

6. Just below this line, you should find the following line:

my $mt_password = 'tbentriespassword';

Replace 'tbentriespassword' with the password chosen in Step 4 (the password should be enclosed in single quotes).

7. Search for "OPTIONS" and choose the options that you want by setting them to 1 or 0. Options include: create new category, default blog, default category, use MT-Blacklist, and create trackback.

8. Save the file and upload to '/lib/MT/App/' within your MT directory (same directory as "Trackback.pm")

9. Begin using the tags described above to inform your visitors of the TrackbackEntry URLs for your entries and categories.

10. Test it out be asking someone to send you a TrackbackEntry ping. (If you want me to send you a test ping, let me know)

Displaying TrackbackEntries

For displaying TrackbackEntries, it is important to understand what data gets stored in which entry fields:

-the Ping Excerpt gets stored in the Entry Body field.
-the Ping Blog Name gets stored in the Extended Entry field.
-the Ping Source URL gets stored in the Excerpt field.
-the Ping Remote IP gets stored in the Keyworda field.

As such you can use the associated MT template tags to display the entries. If you want to display a list of entries that are mixed between your own entries and TrackbackEntries, you may want to make use of the Compare plugin like this:

<MTIfNotEqual a="[MTEntryAuthor]" b="tbentriesusername">
<a href="<$MTEntryAuthorURL$>"><$MTEntryAuthor$></a>
</MTIfNotEqual>
<MTIfEqual a="[MTEntryAuthor]" b="tbentriesusername">
<MTIfEqual a="[MTEntryExcerpt no_generate='1']" b="">
<$MTEntryMore convert_breaks="0"$>
</MTIfEqual>
<MTIfNotEqual a="[MTEntryExcerpt no_generate='1']" b="">
<a href="<$MTEntryExcerpt no_generate="1"$>"><$MTEntryMore convert_breaks="0"$></a>
</MTIfNotEqual>
</MTIfEqual>

The above template snippet displays a linked version of the author's. In the case of TrackbackEntries, the blog name is used as the author name and the source URL is used as the author URL.

Please let me know what you think.

Version History

0.5
-Initial release
0.6
-recording of trackback is now optional
-category creation
-MT-Blacklist support

MTTrackbackEntry is a Movable Type plugin and hack that enables you to create new entries from the Trackbacks that you receive. In other words, it enables other people to post new entries in your blog, simply by pinging an entry or category on your blog. The title of this plugin/hack could just as easily be called TrackbackCrosspost, since it can act as a trackback-based cross-posting tool.

Currently, entries are created AND pings are received and recorded. This means that TrackbackEntry will receive and record pings the same as usual, but it will also add a new entry. Perhaps a future version will only add new entries, or at least provide an option in this area.

TrackbackEntry is especially useful when used to ping Categories rather than entries. When a category is pinged, the new entry is added to that category. This provides more control over the display of Trackback-Entries (display in sidebar, sub-page, etc.)

Template Tags

There are only two new tags provided (because most of functionality lies in the scripts, not in the plugin itself). The following tags enable you to output the TrackbackEntry URLs for entries and categories:

<MTEntryTrackbackEntryLink> - Similar to <MTEntryTrackbackLink>, this tag will display the TrackbackEntry URL for a particular entry. Others can use this URL to to send a TrackbackEntry ping, which will create a Trackback record for the entry and create a new entry in the blog.

<MTCategoryTrackbackEntryLink> - Similar to <MTCategoryTrackbackLink>, this tag will display the TrackbackEntry URL for a particular category. Others can use this URL to to send a TrackbackEntry ping, which will create a Trackback record for the category and create a new entry in the category.

Installation

1. Download Now:

MTTrackbackEntry.zip and extract the files.

Membership required, please sign-in or register:

2. Place "mt-tbentry.cgi" in your MT directory (same directory as mt.cgi). Then CHMOD to 755.

3. Place "TrackbackEntry.pl" in your "plugins" directory within your MT directory.

4. Create a new user to be be used for Trackback-Entries. Make note of the username and password. Give the user permisions to post and rebuild files on each of the blogs that you want to enable TrackbackEntry.

5. Open "TrackbackEntry.pm" and find the line that reads:

my $mt_username = 'tbentriesusername';

Replace 'tbentriesusername' with the user name chosen in Step 4 (the username should be enclosed in single quotes). (remember that MT usernames are case-sensitive)

6. Just below this line, you should find the following line:

my $mt_password = 'tbentriespassword';

Replace 'tbentriespassword' with the password chosen in Step 4 (the password should be enclosed in single quotes).

7. Save the file and upload to '/lib/MT/App/' within your MT directory (same directory as "Trackback.pm")

8. Begin using the tags described above to inform your visitors of the TrackbackEntry URLs for your entries and categories.

9. Test it out be asking someone to send you a TrackbackEntry ping. (If you want me to send you a test ping, let me know)

Displaying TrackbackEntries

For displaying TrackbackEntries, it is important to understand what data gets stored in which entry fields:

-the Ping Excerpt gets stored in the Entry Body field.
-the Ping Blog Name gets stored in the Extended Entry field.
-the Ping Source URL gets stored in the Excerpt field.
-the Ping Remote IP gets stored in the Keyworda field.

As such you can use the associated MT template tags to display the entries. If you want to display a list of entries that are mixed between your own entries and TrackbackEntries, you may want to make use of the Compare plugin like this:

<MTIfNotEqual a="[MTEntryAuthor]" b="tbentriesusername">
<a href="<$MTEntryAuthorURL$>"><$MTEntryAuthor$></a>
</MTIfNotEqual>
<MTIfEqual a="[MTEntryAuthor]" b="tbentriesusername">
<MTIfEqual a="[MTEntryExcerpt no_generate='1']" b="">
<$MTEntryMore convert_breaks="0"$>
</MTIfEqual>
<MTIfNotEqual a="[MTEntryExcerpt no_generate='1']" b="">
<a href="<$MTEntryExcerpt no_generate="1"$>"><$MTEntryMore convert_breaks="0"$></a>
</MTIfNotEqual>
</MTIfEqual>

The above template snippet displays a linked version of the author's. In the case of TrackbackEntries, the blog name is used as the author name and the source URL is used as the author URL.

Please let me know what you think.