wp-cli/import-command
Imports content from a given WXR file., (*1)
, (*2)
Quick links: Using | Installing | Contributing | Support, (*3)
Using
wp import <file>... --authors=<authors> [--skip=<data-type>]
Provides a command line interface to the WordPress Importer plugin, for
performing data migrations., (*4)
Use define( 'IMPORT_DEBUG', true );
for more verbosity during importing., (*5)
OPTIONS, (*6)
<file>...
Path to one or more valid WXR files for importing. Directories are also accepted.
--authors=<authors>
How the author mapping should be handled. Options are 'create', 'mapping.csv', or 'skip'. The first will create any non-existent users from the WXR file. The second will read author mapping associations from a CSV, or create a CSV for editing if the file path doesn't exist. The CSV requires two columns, and a header row like "old_user_login,new_user_login". The last option will skip any author mapping.
[--skip=<data-type>]
Skip importing specific data. Supported options are: 'attachment' and 'image_resize' (skip time-consuming thumbnail generation).
EXAMPLES, (*7)
# Import content from a WXR file
$ wp import example.wordpress.2016-06-21.xml --authors=create
Starting the import process...
Processing post #1 ("Hello world!") (post_type: post)
-- 1 of 1
-- Tue, 21 Jun 2016 05:31:12 +0000
-- Imported post as post_id #1
Success: Finished importing from 'example.wordpress.2016-06-21.xml' file.
Installing
This package is included with WP-CLI itself, no additional installation necessary., (*8)
To install the latest version of this package over what's included in WP-CLI, run:, (*9)
wp package install git@github.com:wp-cli/import-command.git
Contributing
We appreciate you taking the initiative to contribute to this project., (*10)
Contributing isnât limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation., (*11)
For a more thorough introduction, check out WP-CLI's guide to contributing. This package follows those policy and guidelines., (*12)
Reporting a bug
Think youâve found a bug? Weâd love for you to help us get it fixed., (*13)
Before you create a new issue, you should search existing issues to see if thereâs an existing resolution to it, or if itâs already been fixed in a newer version., (*14)
Once youâve done a bit of searching and discovered there isnât an open or fixed issue for your bug, please create a new issue. Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, review our bug report documentation., (*15)
Creating a pull request
Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project., (*16)
Once you've decided to commit the time to seeing your pull request through, please follow our guidelines for creating a pull request to make sure it's a pleasant experience. See "Setting up" for details specific to working on this package locally., (*17)
Support
GitHub issues aren't for general support questions, but there are other venues you can try: https://wp-cli.org/#support, (*18)
This README.md is generated dynamically from the project's codebase using wp scaffold package-readme
(doc). To suggest changes, please submit a pull request against the corresponding part of the codebase., (*19)