wp comment approve

in this article we are going to learn how to use WP comment approve subcommand.

if someone comment on any article then it is available in the comments post type in the WordPress backend.

We can approve, remove or mark that comment as a spam from the backend.

But with the help of WP comment approve CLI command we can approve any comment with the help of the comment ID.

We can use WP comment list command to see all the existing comments and there IDs.

Let’s see it with a simple example.

Suppose we have a comment with id 1243 and we want to approve it with the help of WP CLl command.

# Approve comment.
$ wp comment approve 1243
Success: Approved comment 1243.

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.