SymPress WP-CLI Console

Symfony Console wrappers for useful WP-CLI workflows in SymPress WordPress kernel applications.

The package exposes common WP-CLI operations as Symfony Console commands. It is distributed as a Composer-powered WordPress MU plugin and integrates with the SymPress kernel service container.

Installation

composer require sympress/wp-cli-console

The package requires PHP 8.5, WordPress 6.9 or newer, sympress/kernel, and symfony/console.

Features

• Symfony Console commands backed by WP-CLI
• Automatic use of the local vendor/bin/wp binary when available
• Object cache and rewrite rule maintenance commands
• Plugin, theme, user, cron, option, and database inspection commands
• Streaming stdout and stderr handling for long-running WP-CLI processes
• Kernel service registration through SymPress\WpCliConsole\WpCliConsoleBundle

Commands

wp:cache:flush       Flush the WordPress object cache
wp:rewrite:flush     Flush WordPress rewrite rules
wp:info              Show WP-CLI runtime information
wp:plugin:list       List installed plugins
wp:theme:list        List installed themes
wp:user:list         List WordPress users
wp:cron:list         List scheduled cron events
wp:option:get        Read a WordPress option
wp:db:size           Show WordPress database size

Usage

When the SymPress kernel discovers the package, it registers SymPress\WpCliConsole\WpCliConsoleBundle and loads wp-cli-console/wp-cli-console.php as the MU plugin entry point.

Commands are autoconfigured from src/Command and can be run through the project's Symfony Console entry point:

bin/console wp:plugin:list --status=active --format=table
bin/console wp:option:get siteurl --format=json
bin/console wp:rewrite:flush --hard

The runner executes WP-CLI from the kernel project directory and falls back to the global wp binary when vendor/bin/wp is not executable.

Development

composer install
composer qa

License

This package is licensed under GPL-2.0-or-later.

Positional value validation

Externally supplied positional option names are validated before invoking the runner: empty/whitespace-only names, NUL, and leading option flags (including --exec, --require, --ssh, --path, --url and short flags) are rejected. Legitimate underscore/hyphen option names remain accepted. Runner-generated global/options arguments continue to be passed as argv entries; shell escaping alone cannot prevent WP-CLI global flag injection through an untrusted positional value.