TP2WP Importer

More Info: WordPress Codex: Importing Content

More Info: tp2wp.com/faq

1.1

• Tested compatibility through WordPress 5.2.2

1.0.12

• When multiple TypePad posts have the same post name, we now generate
  a new unique postname for the duplicately named post(s). This means that
  all posts will be imported those, even those sharing the same post name /
  slug (though some incoming links will be broken).
• Small optimization to avoid needing to download duplicate linked to files.
• Small formatting fixes / corrections

1.0.11

• Avoid trying to perform redundant symlinks / copies to existing files
  when creating the legacy (ie /.a./) style links.

1.0.10

• Handle rewriting links to popup versions of images within the plugin
  (previously was only handled in the coversion
  process.
• Remove some redundant checking on remote mimetypes, for some quicker
  imports.
• Small, code-style cleanups

1.0.9

• Handle much larger data sets by doing some array operations in the database instead of in PHP. Specifically, find out which posts still need to be imported by using a nested query instead of to different queries and an array_diff, which hits memory limits much quicker.

1.0.8

• Fix non-fatal error in attachment importer when referencing an undefined array (ie remove some code cruft).
• Some further code formatting to match WordPress coding standards.

1.0.7

• Further improve duplicate post detection by only using the post_name column, which we’re sure will exist since its in Typepad data (as BASENAME). This allows us to avoid an expensive un-indexed query against post_title.

1.0.6

• Improve duplicate post detection method to avoid false positives (previously the importer only checked for posts matching by title and date, which didn’t work well with Typepad’s exported data, where the drafts and posts have the same date)

1.0.5

• Remove a non-fatal error by having the TP2WP_Import::bump_request_timeout() signature match the parent, WP_Importer::bump_request_timeout($val) signature.
• Add support for bzip2’ed .wxr uploads.
• Fix fatal error when zip module wasn’t loaded / available.

1.0.4

• Symlink / copy all files into a flat directory structure too, to allow for redirection rules from .a/ (in TypePad) to wp-content/uploads/tp2wp-migration/.
• Also add in-pluguin URL redirection from Typepad attachment URLs to WordPress attachment URLs (when the WordPress equivalent exists in the above described directory)
• Add several checks to the status page (pretty urls, supports symlinks, etc)
• Fix issue with uploaded, zip’ed wxr files are not properly processed.

1.0.3

• Further corrections to plugin title in WordPress admin.

1.0.2

• Corrections to plugin title and attribution in WordPress admin.

1.0.1

• Updates to Status Check portion of the plugin.

1.0.0

• Initial release of new plugin. The ReadyMade WordPress Importer is superseded by this plugin.

WordPress Importer

Step 2 of our import process is a branch of the default WordPress importer. Our version modifies the default in three ways:

1. If there is an attachment in the WXR and the importer is not able to determine the file type from the file name (ie missing extension), the patched version will make a light (body-less) request to the web server where the file is hosted for information we can use about the file. The things we’re interested in are file type, size, and filename.
2. If the importer is processing an attachment under the above situation, and it is able to determine the file type, then it will rewrite the local version of the file to have the appropriate file extension.
3. When moving from one host to another, or from WordPress.com to a self-hosted site, you may setup hosting for your domain, let’s call it “yourdomain.com” for example, before publicly directing the DNS to the new server. This is the correct thing to do if importing using WXR files. However, some hosts will then process references to “yourdomain.com” as internal references, rather than links to outside resources. This means that the importation process is essentially short circuited, with the public version of “yourdomain.com” being invisible to your new server. The ReadyMade WordPress Importer solves this problem by using TW2WP.com servers to identify the public IP of the source server and then uses that IP, rather than the domain, to import files.