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 usersimport_allow_fetch_attachments: return false if you do not wish to allow importing and downloading of attachmentsimport_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 chosenimport_end: called after the last output from the importer
FAQ
- Installation Instructions
-
The quickest method for installing the importer is:
- Visit Tools -> Import in the WordPress dashboard
- Click on the WordPress link in the list of importers
- Click “Install Now”
- Finally click “Activate Plugin & Run Importer”
If you would prefer to do things manually then follow these instructions:
- Upload the
wordpress-importerfolder to the/wp-content/plugins/directory - Activate the plugin through the ‘Plugins’ menu in WordPress
- 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.
Reviews
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.
Simple
This plugin is very basic in features but works.
I think all wp dev dead with this error
Notice: wp_get_http is deprecated since version 4.4.0! Use WP_Http instead.
The only importer that worked on a WordPress.com site
I tried 3 other highly rated importers and none would support the xml exported from a WordPress.com site. Finally this one worked.
Not bad plugin
Not bad plugin
Not the one I need
I can’t even give a 3 star on this plugin. Using this one is really not practical.
Contributors & Developers
“WordPress Importer” is open source software. The following people have contributed to this plugin.
Contributors“WordPress Importer” has been translated into these 42 locales: French, Turkish, Japanese, Indonesian, German, Korean, Finnish, Russian, Croatian, Catalan, Portuguese, Arabic, Chinese (China), Brazilian Portuguese, Esperanto, Spanish, Italian, Hebrew, Thai, Swedish, Hungarian, Malay, Greek, Dutch, Albanian, Czech, Bosnian, Slovak, Chilean Spanish, Venezuelan Spanish, Peruvian Spanish, Romanian, Welsh, Norwegian (Nynorsk), English (UK), Icelandic, English (Canada), Azerbaijani, Pashto, English (Australia), Lithuanian, English (New Zealand). Thank you to the translators for their contributions.
Translate “WordPress Importer” into your language.
Interested in development?
Browse the code or subscribe to the development log by RSS.
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