WP-CLI warning: version command redeclares global --debug option
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
Research direction
Read the OPTIONS docblock in src/Cli/Commands/Version.php and check how the version command handles WP-CLI's global --debug option. Remove the redundant declaration while preserving the existing debug output behavior; verify that loading BackWPup with a WP-CLI command such as wp plugin list no longer emits the warning.
Written by the indexing model from the issue text.
Description
Environment
- BackWPup 5.7.8
- WordPress 7.1.4
- PHP 8.5.12
- WP-CLI nightly 3.0.0-alpha-79914d9
Steps to reproduce
- Activate BackWPup.
- Run a WP-CLI command that loads active plugins, for example
wp plugin list, using the nightly version above.
Actual behavior
The following warning is printed:
Warning: The `backwpup version` command is registering an argument '--debug' that conflicts with a global argument of the same name.
The warning also appears during unrelated commands, repeatedly adding noise to automated maintenance logs.
Running the command with --skip-plugins=backwpup removes the warning.
Expected behavior
BackWPup's CLI commands should register without warnings while retaining support for WP-CLI's global debugging option.
Likely cause
The OPTIONS docblock in src/Cli/Commands/Version.php explicitly declares [--debug], although WP-CLI already provides this option globally.
Please remove the redundant declaration while preserving the existing debug output behavior.
- Dominant language
- PHP
- Stars
- 96
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wp-media/backwpup
-
S3 backup list times are shifted by the site's UTC offset (timezone offset applied twice)May be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
WordPress XML export: posts have no categories or tags since 5.6.6Possibly taken @rafaelmaeuer claimed this 14 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Complete restore can leave the site half-restoredPossibly taken @rafaelmaeuer claimed this 14 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Complete restore stops after the file step: user is logged out, database is not restoredPossibly taken @rafaelmaeuer claimed this 14 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Database restore loses data when a row is larger than max_allowed_packetPossibly taken @rafaelmaeuer claimed this 14 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in wp-media/backwpup
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[Sync EN] Formatting improvements to "Large Objects (LOBs)" docs (#6056)Possibly taken A pull request linked to this issue is open or already merged. Opensync-en
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
repo:cms
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
craftcms/cms#20613 · 1 comment ·
Maintainers usually reply within 1 day