WordPress Importer

Description

The WordPress Importer will import the following content from a WordPress export file:

  • Posts, pages and other custom post types
  • Comments
  • Custom fields and post meta
  • Categories, tags and terms from custom taxonomies
  • Authors

For further information and instructions please see the Codex page on Importing Content

Filters

The importer has a couple of filters to allow you to completely enable/block certain features:

  • import_allow_create_users: return false if you only want to allow mapping to existing users
  • import_allow_fetch_attachments: return false if you do not wish to allow importing and downloading of attachments
  • import_attachment_size_limit: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited)

There are also a few actions available to hook into:

  • import_start: occurs after the export file has been uploaded and author import settings have been chosen
  • import_end: called after the last output from the importer

FAQ

Installation Instructions

The quickest method for installing the importer is:

  1. Visit Tools -> Import in the WordPress dashboard
  2. Click on the WordPress link in the list of importers
  3. Click “Install Now”
  4. Finally click “Activate Plugin & Run Importer”

If you would prefer to do things manually then follow these instructions:

  1. Upload the wordpress-importer folder to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to the Tools -> Import screen, click on WordPress
Help! I’m getting out of memory errors or a blank screen.

If your exported file is very large, the import script may run into your host’s configured memory limit for PHP.

A message like “Fatal error: Allowed memory size of 8388608 bytes exhausted” indicates that the script can’t successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time.

For those with shared hosting, the best alternative may be to consult hosting support to determine the safest approach for running the import. A host may be willing to temporarily lift the memory limit and/or run the process directly from their end.

WordPress Codex: Importing Content

Reviews

Rarely works well, but forced to use to migrate from wordpress.com

Obviously Automattic want to keep people on wordpress.com, yet still be able to claim an ‘open’ platform (but where’s the full source code, not just Calypso?), so they provide a sh1t plugin for migration to self-hosted wordpress.org.

It rarely works, let alone well, but seems to be the only tool available. Never use this plugin except to migrate from wordpress.com to self-hosted wordpress.org. Any other tool will always be better for any other job.

wordpress.org is open. wordpress.com is not. Do not use wordpress.com in the first place if you want to save yourself hassle in the long run. (I make money out of people who do, but I shouldn’t have to.)

No sirve

No sirve desde hace mucho tiempo. Si ya no lo piensan actualizar, deberían quitarlo, pero sobre todo, los que venden temas usando éste plugin como necesario, deben buscar un sustituto.

Read all 281 reviews

Contributors & Developers

“WordPress Importer” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

0.6.3

  • Add support for import term metadata.
  • Fix bug that caused slashes to be stripped from imported content.
  • Fix bug that caused characters to be stripped inside of CDATA in some cases.
  • Fix PHP notices.

0.6.2

  • Add wp_import_existing_post filter. See: https://core.trac.wordpress.org/ticket/33721

0.6

  • Support for WXR 1.2 and multiple CDATA sections
  • Post aren’t duplicates if their post_type’s are different

0.5.2

  • Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when
    an export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used.

0.5

  • Import comment meta (requires export from WordPress 3.2)
  • Minor bugfixes and enhancements

0.4

  • Map comment user_id where possible
  • Import attachments from wp:attachment_url
  • Upload attachments to correct directory
  • Remap resized image URLs correctly

0.3

  • Use an XML Parser if possible
  • Proper import support for nav menus
  • … and much more, see Trac ticket #15197

0.1

  • Initial release