From my snooping, Wordpress 2.2.x has a new hook and has changed a hook. Before 2.2, the delete_post hook was called after the post was deleted. With 2.2, delete_post hook is call before the post is deleted whereas a new hook deleted_post is called after the post is deleted. In all the cases, the hook function is passed the post ID.

This is very good because originally you would be out of luck if you needed information (date, slug, etc) about the deleted post. Now you can grab the information, based upon the ID, before the post is deleted from the database.

Although WordPress has a built-in import feature for TypePad/Movable Type, it does not import the slugs. (The slug is the post name formated for the URL for example a post titled “I Love Cheese” has a slug of “i-love-cheese” in WordPress.) The slugs are not export by TypePad nor import by WordPress. So WordPress creates new slugs for each post in the WordPress style. The three issues with this are:

1. TypePad uses the underscore ”_” to separate words whereas WordPress uses the dash ”-”
2. TypePad truncates the slug to 15 characters whereas WordPress does not
3. TypePad will keep slugs that are not the same as the title

The first and second can be easily be fixed with a little bit of SQL on the database. But since the last one requires that you know explicitly the slug in TypePad, a modified import process needs to be done.

(These steps require that you do not have any post in your WordPress installation.)

The Modified Import Process

Exporting From TypePad

The first step is to get an export from TypePad with the slugs included. Adam Stiles has created a Movable Type template for this purpose . I did have to modify it to get all (actually about the last five years which all the post are within) the posts instead of the last 100.

Original:
<MTEntries lastn="100">

Modified:
<MTEntries days="1780">

Please note that this will only export posts which are published. Drafts will not be exported.

Save and publish the template as an Index Template. Then view the generate published file and save it to your computer.

Importing Into WordPress

The second step is to import the exported posts into WordPress. The default WordPress import will not import the slugs. In order to also bring in slugs, you will need to use Adam Stiles Movable Type importer.

1. You must already have WordPress installed and configured.
2. Upload the export posts file to your WordPress installation’s wp-admin directory.
3. Download the MovableType importer and save as import-mt.php.
4. Edit import-mt.php to include the name of the export file. For example if your export file was named export.txt, then modify the second line as such “define('MTEXPORT', 'export.txt');”.
5. Upload import-mt.php to your WordPress installation’s wp-admin directory.
6. Run, through your web browser, import-mt.php in your WordPress installation. (The first page that shows up is not an error, but just a message stating you must edited, which you have, “define('MTEXPORT', '');” before moving to the next step.)

Trim Excess Off Slugs With SQL

(This part of the process assumes that no posts existed in your WordPress installation before you imported the TypePad post into WordPress. Although, I am sure you can still trim the desired posts with SQL code which targets the desired posts.)

The imported slugs are not the actually slugs; instead, they are the relative URL paths which happen to include the slugs. To get the proper slugs we will trim the excess. For this case, the format is ”/YYYY/MM/SLUG.html”. A simple MySQL query can trim this (I did this in phpMyAdmin):

UPDATE <WORDPRESS TABLE PREPEND>_posts SET post_name = INSERT( INSERT(post_name, LOCATE('.html', post_name), 5, ''), 1, 9, '' ) WHERE 1

The break down of the query

• <WORDPRESS TABLE PREPEND> is the value you prefixed your database tables with during the configuration (the default is “wp”).
• The query will update every record (every post). To target posts you will need, at the least, to modify WHERE 1.
• post_name is the post slug field.
• INSERT ( str, pos, length, repstr) is a MySQL function we are using to “erase” part of the string we do not want.
• LOCATE ('.html', post_name) returns the starting position of ”.html” is post_name.
• INSERT(post_name, LOCATE('.html', post_name) returns a string of ”/YYYY/MM/SLUG” which means we erased ”.html”.
• INSERT( INSERT(post_name, LOCATE('.html', post_name), 5, ''), 1, 9, '' ) returns a string “SLUG” which means we erased ”/YYYY/MM/”.

Finally, the imported post have their respected original slugs. Which will make it far easier to mimic the URL structure of the TypePad individual archives with WordPress.