For instance, you can easily update your password using the WP-CLI if your “reset password” link isn’t working. WP-CLI is useful in a variety of circumstances that are similar to each other. Additionally, we simply adore the hacker-like sensation that comes from using the command line.<\/p>\n\n\n\n
In this article, we’ll describe and demonstrate how to complete a few of the generally tedious chores that WP-CLI almost turns into a delightful experience. Let’s get to work!<\/p>\n\n\n\n
Table of Contents:<\/strong><\/p>\n\n\n\n Since this application allows you command-line access to the WordPress administrative system, WP-CLI stands for WordPress Command-Line.<\/p>\n\n\n\n On August 8th, 2018, WP-CLI v2<\/a> was released. If you’re a FastComet customer, WP-CLI v2.0+ is already installed by default on all of our servers. To get started, just SSH into your server. You can be sure that all of our hosting plans include SSH access<\/a>.<\/p>\n\n\n\n Typically, managing a WordPress website manually requires using the online user interface (the wp-admin). Consequently, fixing a malfunctioning site or overseeing a transitional time frequently entails sifting through files using an FTP client<\/a> or attempting to write original PHP code. WP-CLI eliminates the need for additional plugins and streamlines the process of managing your website by providing a direct-access shortcut.<\/p>\n\n\n\n There is a slight learning curve if you have never used the command line before. WP-CLI, however, can greatly speed up how you deal with your website once you get started. With only a few clicks, you can modify complicated databases, plugins, and themes. You can also utilize the plain-text interface to control menus, choices, and comments if you like.<\/p>\n\n\n\n In the end, WP-CLI simplifies and accelerates a variety of challenging activities. Additionally, WP-CLI can be expanded. If you have specific requirements, you can write unique scripts<\/a> that execute using WP-CLI according to your requirements.<\/p>\n\n\n\n Before continuing, it’s crucial to understand that WP-CLI is a server-installed utility rather than a plugin for your WordPress website. In other words, for consistent access, you must install WP-CLI on both your live hosting server and your local development environment.<\/p>\n\n\n\n Using the command line, you can open the folder for the WordPress website you want to control after installing WP-CLI. You’ll need secure shell access<\/a> if you’re working in real-time on your hosting server.<\/p>\n\n\n\n But first, we advise testing these commands in a development setting! Before utilizing this tool on a live server, you should be reasonably comfortable with it because there is no undo option. Here are four helpful ways to practice utilizing WP-CLI on your site to get you started.<\/p>\n\n\n\n When it comes to enabling you to configure a new site, WP-CLI has always been quite effective. For instance, you may create a new config file and include all the necessary information in it using the handy wp config create command<\/a>. usually completed considerably more quickly than the conventional method, especially if you have a quick typing speed.<\/p>\n\n\n\n WP-CLI, however, goes a step further. The primary The first one is this:<\/p>\n\n\n\n This lists constants and globals as defined in your current The other one is this:<\/p>\n\n\n\n This command simply displays a path to the current Another WP-CLI command is available if you wish to interact with your WordPress installation even more closely:<\/p>\n\n\n\n Very helpful in assisting you in determining whether or not you require database improvement.<\/p>\n\n\n\n Running an update often entails login into your admin and visiting a few pages to update your site.<\/p>\n\n\n\n With WP-CLI, updates are easily run with one simple command<\/a>:<\/p>\n\n\n\n The ability to accept parameters to alter the behavior of the method makes it special. Consider the case where you recently updated WordPress to a version that broke a crucial plugin for your website. Although the creator of that plugin hasn’t had a chance to update it yet, your website must function properly. Although updating a site regularly is preferable, you can change the core by adding the version flag to your command and going back to a time when there was no conflict:<\/p>\n\n\n\n Normally, to deactivate a plugin that has fully broken your site (or even just disabled your admin), you must get in via FTP and modify the name of the plugin’s folder. On the other side, deactivating plugins may be done with a simple WP-CLI command<\/a>:<\/p>\n\n\n\n If a plugin is giving you serious trouble and needs to be deleted, you can do so using the delete command instead:<\/p>\n\n\n\n Additionally, you can avoid manual plugin updates by using a command that works similarly to the WordPress core update feature:<\/p>\n\n\n\n Additionally, you can check the status of the plugins that are currently installed on your website using WP-CLI, which is probably something I should have stated at the outset. For that, employ:<\/p>\n\n\n\n These instructions might not seem like they would save a lot of time when used alone. It’s crucial to keep in mind, nevertheless, that visiting the server directly is far quicker than waiting for a web browser to render all the scripts and styles necessary for a graphical user interface. You might be astonished by how quickly your additional time mounts up if you routinely have to do this kind of work.<\/p>\n\n\n\n Consider a scenario where you forgot your WordPress admin password. You’ve attempted the link to reset your password, but for some reason, your mailbox isn’t receiving the reset email. Are you permanently unable to access your WordPress website? With WP-CLI, not so.<\/p>\n\n\n\n With WP-CLI, quick user management is possible, and with the line below, you may reset passwords<\/a>.<\/p>\n\n\n\n There’s no need to freak out or fret about difficult workarounds to regain access to your site with simple commands. The days of manually hashing your password and entering it into the database are long gone.<\/p>\n\n\n\n Additionally, utilizing this method does not compromise the security of your website because everything is done over a secure connection to your server.<\/p>\n\n\n\n Direct database interaction is difficult to achieve with WordPress. When you wish to carry out ostensibly straightforward operations, like running an update without a plugin or looking up and changing a preset phrase, this might be irritating.<\/p>\n\n\n\n To make these tasks simpler, use WP-CLI. You can optimize<\/a> and repair<\/a> databases with straightforward commands like:<\/p>\n\n\n\n If you are writing a custom query, you can quickly test it out by using the query command<\/a>:<\/p>\n\n\n\n However, it’s imperative that you understand how to establish backups before you become very trigger-happy with the database. The command to use in WP-CLI to create SQL backups<\/a> is as follows:<\/p>\n\n\n\n If something goes wrong, you can utilize the SQL file that is created as a backup of your site’s database. Even when used with backup plugins, it performs effectively.<\/p>\n\n\n\n The name that will be provided to the file is somewhat arbitrary. Use this to assign your own:<\/p>\n\n\n\n Working with the database on your site is a breeze, thanks to WP-CLI.<\/p>\n\n\n\n The number of changes on some of our most regularly updated posts exceeds 200, which makes managing them extremely difficult.<\/p>\n\n\n\n The bar at the top appears when you access WordPress’ standard revision comparison page (see below screenshot). You can select the two revisions you want to compare through it. If a post has fewer than 20 revisions, this is OK. However, if there are more than 100, the bar is no longer clickable, making it difficult to quickly select the precise revision you want and necessitating pixel-perfect clicks. The bar is simply too thick.<\/p>\n\n\n\n To battle this in some way, you can set a limit on the number of revisions allowed per post in your And the WP-CLI way is just much quicker. To get started, you need to install an additional WP-CLI package called wp-revisions-cli<\/a>.<\/p>\n\n\n\n An easy command can be used to accomplish this:<\/p>\n\n\n\n After that, you get to use a handful of cool new WP-CLI commands:<\/p>\n\n\n\n That eliminates all posts’ previous revisions. Only the most recent changes are kept by default, which is As an alternative, if you choose to be more involved in the revision process, you can, for example, manage the revisions for a particular post:<\/p>\n\n\n\n This command gives you a list of all the revisions for a given post.<\/p>\n\n\n\n Or:<\/p>\n\n\n\n which deletes edits to a specific post that was made on or before a certain date (YYYY-MM-DD).<\/p>\n\n\n\n Overall, a cool function, especially if you frequently edit your existing posts, which results in numerous revisions. I’m interested to see what future updates the Making child themes is not really challenging. To make sure that some minor details haven’t been altered, you must first check the official reference at Codex<\/a>. Then, you must create a functions.php file, place CSS in a new directory, and so on and so forth.<\/p>\n\n\n\n You can use a a quicker method<\/a> with WP-CLI. You simply do this:<\/p>\n\n\n\n Just that. An operable, blank child theme built on a predetermined parent theme is what you receive as a consequence.<\/p>\n\n\n\n A few extra parameters are also available. For example, you could try this:<\/p>\n\n\n\n Dummy content is something you most likely need rather frequently when working on any kind of WordPress project.<\/p>\n\n\n\n In such situations, I used to typically press Ctrl+F and begin looking for that annoying XML dump of, for instance, WordPress material that I had lying around somewhere.<\/p>\n\n\n\n Anyway, as you\u2019d imagine, WP-CLI has some options for that too:<\/p>\n\n\n\n This command creates 6 empty posts, but you don\u2019t need to stop at just 6 \u2013 WP-CLI promises that 1000 is also a perfectly executable value.<\/p>\n\n\n\n Or, to make things more factual:<\/p>\n\n\n\n The command creates 6 posts, each having 4 paragraphs of dummy lorem ipsum text imported from loripsum.net.<\/p>\n\n\n\n One pretty cool WP-CLI command enables you to completely remove all of the content from your site, including posts, comments, terms, and meta while keeping the users and site setup untouched. This is it:<\/p>\n\n\n\n The amount of time this will save you will be immediately apparent if you frequently utilize the same development WordPress setup for your testing, experiments, etc.<\/p>\n\n\n\n This WP-CLI command is incredibly quick, even if you can get the same result by manually looking through your content or using You could also:<\/p>\n\n\n\n The command gets rid of everything in your \u201cuploads\u201d folder as well.<\/p>\n\n\n\n Using WP-CLI, you can also reinstall WordPress core. The WordPress core would be downloaded without the pre-installed themes and plugins using the following command:<\/p>\n\n\n\n First of all, WP-CLI offers you a variety of options for managing comments. You can, for instance:<\/p>\n\n\n\n However, removing all of the spam comments from your website at once can be the most intriguing thing you can do in this situation. This is very useful if you ever discover that your database has hundreds of brand-new spam comments.<\/p>\n\n\n\n The command is this:<\/p>\n\n\n\n What a clever hack! The ID(s) of the comment(s) that should be deleted is required as an argument for the primary wp comment delete command. Therefore, we are calling another command, wp comment list, which displays a list of all the comments that have been flagged as spam to supply the ID(s).<\/p>\n\n\n\n The standard wp-cron mechanism hasn\u2019t been the most reliable thing. More or less, when you schedule a post in WordPress, you can never be 100% sure that it will indeed go live.<\/p>\n\n\n\n\n\t
\n\t
What is the WP-CLI Project<\/h2>\n\n\n\n
Best WP-CLI Commands to Manage your WordPress Site<\/h2>\n\n\n\n
Look Into the the wp-config.php File<\/h3>\n\n\n\n
wp config<\/code> command has two subcommands.<\/p>\n\n\n\nwp config get<\/code><\/pre>\n\n\n\nwp-config.php<\/code> file.<\/p>\n\n\n![\"WP](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2022\/09\/wp-config-file.png\")
<\/figure>\n<\/div>\n\n\nwp config path<\/code><\/pre>\n\n\n\nwp-config.php<\/code> file.<\/p>\n\n\n\nwp db size --tables<\/code><\/pre>\n\n\n![\"WordPress](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2022\/09\/wp-config-path.png\")
<\/figure>\n<\/div>\n\n\nRun Core Updates<\/h3>\n\n\n\n
wp core update<\/code><\/pre>\n\n\n\nwp core update --version=6.02<\/code><\/pre>\n\n\n![\"WordPress](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2022\/09\/wordpress-core-update-1024x256.png\")
<\/figure>\n<\/div>\n\n\nUpdate, Disable, and Delete Unwanted Plugins<\/h3>\n\n\n\n
wp plugin deactivate plugin-name-example<\/code><\/pre>\n\n\n\nwp plugin delete plugin-name-example<\/code><\/pre>\n\n\n\nwp plugin update --all<\/code><\/pre>\n\n\n\nwp plugin status<\/code><\/pre>\n\n\n\nReset User Passwords<\/h3>\n\n\n\n
wp user update adminuser@example.com --user_pass=new-password-example<\/code><\/pre>\n\n\n\n![\"WP-CLI](\"https:\/\/www.fastcomet.com\/blog\/wp-content\/uploads\/2022\/09\/wp-cli-user-update.png\")
<\/figure>\n\n\n\nBackup and Manipulate the Database<\/h3>\n\n\n\n
wp db optimize<\/code><\/pre>\n\n\n\nwp db repair<\/code><\/pre>\n\n\n\nwp db query \"SELECT * FROM wp_options\"<\/code><\/pre>\n\n\n\nwp db export<\/code><\/pre>\n\n\n\nwp db export yourname.sql<\/code><\/pre>\n\n\n\nClean Post Revisions<\/h3>\n\n\n\n
wp-config.php<\/code> file (eg. define('WP POST REVISIONS', 40)<\/code>;). However, this merely restricts future acts that you take. All current revisions that are higher than that threshold must be removed. There are several ways to accomplish this. One is done using a plugin. The second is through WP-CLI.<\/p>\n\n\n\nwp package install trepmal\/wp-revisions-cli<\/code><\/pre>\n\n\n\nwp revisions clean<\/code><\/pre>\n\n\n\nWP_POST_REVISIONS<\/code>.<\/p>\n\n\n\nwp revisions list --post_id=ID<\/code><\/pre>\n\n\n\nwp revisions clean --post_id=ID --before-date=DATE<\/code><\/pre>\n\n\n\nwp-revisions-cli<\/code> package will offer.<\/p>\n\n\n\nCreate a Child Theme<\/h3>\n\n\n\n
wp scaffold child-theme NEW-CHILD-SLUG --parent_theme=SLUG --theme_name=TITLE<\/code><\/pre>\n\n\n\nwp scaffold child-theme SLUG --parent_theme=SLUG --theme_name=TITLE --author=FULL-NAME --author_uri=URI --theme_uri=URI --activate --force<\/code><\/pre>\n\n\n\n--force<\/code> overwrites files that already exist.<\/li><\/ul>\n\n\n\nCreate Dummy Content for Testing<\/h3>\n\n\n\n
wp post generate --count=6<\/code><\/pre>\n\n\n\ncurl http:\/\/loripsum.net\/api\/4 | wp post generate --post_content --count=6<\/code><\/pre>\n\n\n\nBlank Your Site<\/h3>\n\n\n\n
wp site empty<\/code><\/pre>\n\n\n\nphpMyAdmin<\/code>.<\/p>\n\n\n\nwp site empty --uploads<\/code><\/pre>\n\n\n\nReinstall WordPress Core<\/h3>\n\n\n\n
wp core download --skip-content --force<\/code><\/pre>\n\n\n\nRemove All Spam Comments<\/h3>\n\n\n\n
wp comment delete $(wp comment list --status=spam --format=ids)<\/code><\/pre>\n\n\n\nTame wp-cron<\/h3>\n\n\n\n