how to use wp-cli

There is a commandline version of the admin tools, called wp-cli, that you can install. However it does not let you run as "root", you have to turn into the web user to run it.


Instruction manual here:


https://developer.wordpress.org/cli/commands/plugin/


https://developer.wordpress.org/cli/commands/theme/


Here are some example commands:


Force a theme update:


sudo -u www-data -i -- wp theme update theme_name --path="/var/www/html/"


Install a plugin (force update):


sudo -u www-data -i -- wp  plugin install akismet --force --path="/var/www/html/"


Bulk install plugins:


cd /var/www/html/wp-content/


for i in `/bin/ls plugins` ; do (  sudo -u www-data -i -- wp  plugin install $i  --force --path="/var/www/html/" ) ; done


Bulk enable or disable plugins:


cd /var/www/html/wp-content/


for i in `/bin/ls plugins` ; do (  sudo -u www-data -i -- wp  plugin toggle $i  --force --path="/var/www/html/" ) ; done


Reinstall the entire site:


sudo -u www-data -i -- wp core download --skip-content --force

sudo -u www-data -i -- wp core update-db --path="/var/www/html"

sudo -u www-data -i -- wp core update --version=x.x --force


note you can leave out the --version and it will go to the latest.

Popular posts from this blog

forcing deactivating of plugins via mysql

 In the WordPress database, you find there's a table called wp_options inside that table is an option called active_plugins . You can see it by typing: mysql> describe wp_options; This will show the following structure: +--------------+-----------------+------+-----+---------+----------------+ | Field        | Type            | Null | Key | Default | Extra          | +--------------+-----------------+------+-----+---------+----------------+ | option_id    | bigint unsigned | NO   | PRI | NULL    | auto_increment | | option_name  | varchar(191)    | NO   | UNI |         |                | | option_value | longtext        | NO   |     | NULL    |                | | autoload     | varchar(20)     | NO   | MUL | yes     |                | +--------------+-----------------+------+-----+---------+----------------+ The relevant option is called active_plugins , so to see its content, type: mysql> select * from wp_options where option_name = "active_plugins"; This will retu
Read more

turning on debug mode

Turn debug mode on edit your wp-config.php file and find define('WP_DEBUG', false); change to define('WP_DEBUG', true); General causes of bugs 1. Dodgy plugins/templates. Remove them all and add them back one at a time. Same for themes 2. Config errors. Replace the config.php file with the template and reinstate it. Obviously copy/paste the login details for the database out before you do that, so when you recreate it, it asks for them again. 3. Code incompatibilities . You have some old code somewhere (e.g. an old php file) which was not upgraded and is now incompatible with the new php in the new issue of wordpress/plugin/template etc 4. Permission errors.  chmod -R 755 /var/www/mysite chown -R www-data:www-data /var/www/mysite assuming your installation is located in /var/www/mysite. On a single-site server it will be /var/www/html "There has been a critical error on your website" = problem 3 above, usually.
Read more