wp term migrate

Migrate a term of a taxonomy to another taxonomy.

View Open Issues (0) View Closed Issues (0)
Create New Issue

OPTIONS OPTIONS

<term>
Slug or ID of the term to migrate.
[--by=<field>]
Explicitly handle the term value as a slug or id.
---
default: id
options:
– slug
– id
---
[--from=<taxonomy>]
Taxonomy slug of the term to migrate.
[--to=<taxonomy>]
Taxonomy slug to migrate to.

Top ↑

EXAMPLES EXAMPLES

# Migrate a category's term (video) to tag taxonomy.
$ wp term migrate 9190 --from=category --to=post_tag
Term '9190' migrated!
Old instance of term '9190' removed from its original taxonomy.
Success: Migrated the term '9190' from taxonomy 'category' to taxonomy 'post_tag' for 1 posts

Top ↑

GLOBAL PARAMETERS GLOBAL PARAMETERS

These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.

Argument Description
--path=<path> Path to the WordPress files.
--url=<url> Pretend request came from given URL. In multisite, this argument is how the target site is specified.
--ssh=[<scheme>:][<user>@]<host\|container>[:<port>][<path>] Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “vagrant”).
--http=<http> Perform operation against a remote WordPress installation over HTTP.
--user=<id\|login\|email> Set the WordPress user.
--skip-plugins[=<plugins>] Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.
--skip-themes[=<themes>] Skip loading all themes, or a comma-separated list of themes.
--skip-packages Skip loading all installed packages.
--require=<path> Load PHP file before running the command (may be used more than once).
--[no-]color Whether to colorize the output.
--debug[=<group>] Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.
--prompt[=<assoc>] Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.
--quiet Suppress informational messages.

Command documentation is regenerated at every release. To add or update an example, please submit a pull request against the corresponding part of the codebase.