--skip-plugins is ignored on WordPress 7.0.4 and higher under specific circumstances.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Start by reproducing the three listed commands with a premium plugin lacking a valid license on WordPress 7.0.4 or 7.1, then compare the first and second --skip-plugins runs. Done means repeated runs report the same failed update result instead of incorrectly reporting that the plugin is already updated.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bug Report
- Yes, I reviewed the contribution guidelines.
- Yes, more specifically, I reviewed the guidelines on how to write clear bug reports.
Describe the current, buggy behavior
We have automated updates using WP-CLI on our hosting-cluster. We notice that since August 20th, this behaviour is occurring on a lot of sites of customer that have built their sites with a premium plugin but lack a valid license or have an expired license.
How it occurs
Every night we run several wp-cli commands to deploy updates of plugins and themes. We use WP-CLI for this, obviously.
# wp plugin update js_composer
Onderhoudsmodus inschakelen...
Warning: Update pakket niet beschikbaar.
Onderhoudsmodus uitschakelen...
+-------------+-------------+-------------+--------+
| name | old_version | new_version | status |
+-------------+-------------+-------------+--------+
| js_composer | 8.3.1 | 9.0.1 | Error |
+-------------+-------------+-------------+--------+
Error: No plugins updated (1 failed).
So at this point, to ensure we do not hit a blocking factor due to a plugin conflict, we'll repeat the command with the --skip-plugins option:
# wp plugin update js_composer --skip-plugins
Onderhoudsmodus inschakelen...
Warning: Update pakket niet beschikbaar.
Onderhoudsmodus deactiveren...
+-------------+-------------+-------------+--------+
| name | old_version | new_version | status |
+-------------+-------------+-------------+--------+
| js_composer | 8.3.1 | 9.0.1 | Error |
+-------------+-------------+-------------+--------+
Error: No plugins updated (1 failed).
Now here's the weird thing. If you then run that same command again, this suddenly declares that the plugin did update (even when it did not):
Success: Plugin already updated.
This only occurs on the second time you run the same command with the --skip-plugins option.
We have seen this occur consistently on several premium plugins in combination with WordPress 7.0.4 or 7.1. We did not see this behaviour in combination with earlier versions of core.
Describe how other contributors can replicate this bug
To replicate you'll need these things:
- a premium plugin (WPBakery Page Builder, Elementor Pro) that has an update available, but has no valid license.
- WordPress 7.0.4 or 7.1
How to replicate:
(for this example I'll assume you are also testing with js_composer, update your plugin name accordingly when testing with another plugin)
- Run: wp plugin update js_composer
- Run: wp plugin update js_composer --skip-plugins
- Run: wp plugin update js_composer --skip-plugins
Expected outcome
The first two commands will result in:
Error: No plugins updated (1 failed).
The third command will result in:
Success: Plugin already updated.
Let us know what environment you are running this on
# wp cli info
OS: Linux 6.1.182-hcl #deb11 SMP Fri Aug 7 06:55:11 UTC 2026 x86_64
Shell: /bin/bash
PHP binary: /usr/local/php-7.4/bin/php
PHP version: 7.4.33
php.ini used: /data/jail/usr/local/php-7.4/etc/php.ini
MySQL binary: /usr/local/bin/mysql
MySQL version: mysql Ver 14.14 Distrib 5.7.44-57, for debian-linux-gnu (x86_64) using 8.1
SQL modes:
WP-CLI root dir: phar://wp-cli.phar/vendor/wp-cli/wp-cli
WP-CLI vendor dir: phar://wp-cli.phar/vendor
WP_CLI phar path: phar:///usr/bin/wp
WP-CLI packages dir: /data/sites/web/REDACTED/.wp-cli/packages/
WP-CLI cache dir: /data/sites/web/REDACTED/.wp-cli/cache
WP-CLI global config:
WP-CLI project config:
WP-CLI version: 2.12.0
Sadly I'm not able to provide a solution just yet, as I am still trying to figure out where the cause originates.
- Lenguaje dominante
- Gherkin
- Estrellas
- 90
- Forks
- 88
- Merge medio
- 2 d 3 h
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de wp-cli/extension-command
-
command:plugin-update command:theme-update
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
wp-cli/extension-command#555 · 2 comentarios ·
-
opcache invalidationPosiblemente ocupada @swissspidy la tomó hace 230 días. Abiertocommand:plugin-update command:theme-update
wp-cli/extension-command#444 · 10 comentarios · 1 reacción · 2 asignados ·
-
Add wp theme cache commandQuizá libre de nuevo @swissspidy la tomó hace 242 días y no hay ningún pull request abierto. Abiertocommand:theme state:unconfirmed
wp-cli/extension-command#392 · 9 comentarios · 1 reacción · 2 asignados ·
Todos los issues de wp-cli/extension-command
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Doist/todoist-cli#576 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
🐛 Bug supabase/cli
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día