wp cli update should be run when provisioning a box about wp-vagrant HOT 3 CLOSED

Development boxes should be fairly static and don't change by themselves in general. Otherwise the promise that 'vagrant up' will magically create a identical dev environment for each developer would not hold. For Vagrant the designed way to upgrade, is to run vagrant box update so that when developers get an updated server software stack, they all at least get the same new stack.

The originially reported issue is now fixed as WP-CLI is available in the next Vagrant image.

from wp-vagrant.

This is probably related to wp-cli being outdated. Trying to run wp plugin install one-time-login --activate results in

PHP Fatal error:  Uncaught Error: Call to undefined function apply_filters() in /data/wordpress/htdocs/wordpress/wp-includes/load.php:317

Which in turn is caused by WP 4.6. Easy fix is running sudo wp cli update on the vagrant machine.

from wp-vagrant.

Should be fixed by just updating your box.

However it's a good idea to always run wp cli update on provision, just to make sure. I'm not going to close this issue yet.

from wp-vagrant.