DE

↑ ↓ select, Enter open, Esc close

Change the role of a WordPress user

cautionWP-CLIalle

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
user@server
wp user set-role editorial editor --path=/var/www/vhosts/example.com/httpdocs

Replaces all existing roles of the user with the given role. The user can be specified by login, email or ID. Common roles are administrator, editor, author, contributor and subscriber.

Note: Demoting the last administrator locks you out of the dashboard. Check with wp user list --role=administrator first.

Also searched as

  • remove admin rights wordpress
  • make wordpress user administrator
  • change user role without login

Related one-liners

All in WP-CLI

List all WordPress users with their roles

$wp user list --fields=ID,user_login,user_email,roles --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Create a new WordPress administrator

$wp user create emergencyadmin admin@example.com --role=administrator --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

List all WordPress administrators

$wp user list --role=administrator --fields=ID,user_login,user_email,user_registered --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Reset a WordPress user password

$wp user update admin --user_pass=NewSecurePassword --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Show recently registered WordPress users

$wp user list --orderby=registered --order=DESC --fields=ID,user_login,user_email,user_registered,roles --path=/var/www/vhosts/example.com/httpdocs | head -n 15
harmlessWP-CLI

Back up the WordPress database as a gzip file

$wp db export - --path=/var/www/vhosts/example.com/httpdocs | gzip > /var/www/vhosts/example.com/db-backup.sql.gz
harmlessWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.