update using wp-cli fails for one site out of many I manage

Hi @spinhead,

That’s strange indeed. I’ve tried replicating this using a fresh WP environment with the 8.3.0.1 version of the plugin, but everything works fine here. Here’s the output I got.

[] $ wp plugin list --update=available
+-------------------+--------+-----------+---------+
| name              | status | update    | version |
+-------------------+--------+-----------+---------+
| really-simple-ssl | active | available | 8.3.0.1 |
+-------------------+--------+-----------+---------+
[] $ wp plugin update really-simple-ssl
Onderhoudsmodus inschakelen...
Update aan het downloaden van https://downloads.www.ads-software.com/plugin/really-simple-ssl.9.0.2.zip...
De update aan het uitpakken...
De laatste versie installeren...
Verwijderen van oudere versie van de plugin...
Plugin succesvol geüpdatet.
Onderhoudsmodus uitschakelen...
+-------------------+-------------+-------------+---------+
| name              | old_version | new_version | status  |
+-------------------+-------------+-------------+---------+
| really-simple-ssl | 8.3.0.1     | 9.0.2       | Updated |
+-------------------+-------------+-------------+---------+
Success: Updated 1 of 1 plugins.

The main difference compared to your output appears to be that it is updating the plugin to version 9.0.0 instead of 9.0.2, the latest version. Perhaps you can run wp core check-update first, to refresh the update cache for WordPress Core, Plugins and Themes, and then check if the new update became available by running wp plugin list --update=available, and attempt to update the plugin once more.

But as your other environments don’t experience this issue, nor do I seem to be able to replicate this on a fresh test environment, this would lead me to suspect that it is isolated to that one specific environment.

Kind regards, Jarno

Core is always updated before plugins. No errors.

“lead me to suspect that it is isolated to that one specific environment.”

That’s what I stated in my post. Not looking for someone to reproduce the error since it is isolated to this specific environment. As posted, asking for suggestions to troubleshoot and isolate what it is about this specific environment that is creating a conflict between wp-cli and the plugin.

Mistake on my part: TWO of my sites are affected. Added the address of the other to the original post in an edit.

Hi @spinhead,

I understand, and with the command wp core check-update I did not intend for you to update WordPress Core, but the goal was to ‘force refresh’ the update cache for plugins and themes; so that the latest version of the plugin (9.0.2) hopefully becomes available.

What you could try to obtain some more information about the potential culprit is to run the update command with the --debug flag added, to increase the verbosity of the output: wp plugin update really-simple-ssl --debug

Kind regards, Jarno

Ah. I misunderstood.

The debug option should have been obvious. Since I’ve already updated the plugin manually I suspect the debug info won’t be meaningful, but I will modify my script to include it and gather the info next time there’s an update.

mea culpa

it appears the culprit was the PHP version in bashrc on both accounts. mind you, other accounts have the same PHP version in bashrc and work fine, but changing it on these seems to have resolved the existing issue.

thank you for your patience and pointers.

Hi @spinhead,

Glad to hear that you’ve been able to solve this in the meantime, appreciate the update as well!

Kind regards, Jarno