WP-CLI's search-replace command can be used to perform batch replacement operations on WordPress databases, especially for migrating sites or updating serialized data. 1. Use the basic command wp search-replace 'old-string' 'new-string' to replace strings globally and process serialized data correctly; 2. Use wp db export to back up the database before execution; 3. Use the --dry-run option to test run to view the changed content without actually modifying it; 4. Use --skip-columns or --include-columns to define the replacement range to avoid affecting irrelevant fields; 5. Support SSL migration and case-insensitive replacement, and use the https://example.com target address and --case-insensitive parameters to control behavior respectively. Reasonable use of these functions can effectively complete database batch modification tasks while ensuring safety.
If you're managing a WordPress site and need to make bulk changes across your database, WP-CLI's search-replace
command is one of the most powerful tools at your disposal. It's especially useful when migrating a site from one domain to another or updating serialized data that regular find-and-replace methods can't handle.
Here's how to use it effectively without breaking anything.
Understanding the Basics of wp search-replace
The core command looks like this:
wp search-replace 'old-string' 'new-string'
By default, this command searches every table in your WordPress database for old-string
and replaces it with new-string
. It handles serialized data correctly, which is one of the big advantages over doing a manual SQL find/replace.
Before running it on a live environment, always back up your database first. You can do that quickly with:
wp db export
This way, if something goes wrong, you can roll back easily.
When to Use the --dry-run
Option
Before making real changes, test your command with the --dry-run
flag:
wp search-replace 'old-url.com' 'new-url.com' --dry-run
This shows you what would be updated without actually modifying the database. It's a great way to double-check that you're targeting the right strings and won't accidentally replace something unintended.
Some common scenarios where this helps:
- Checking if old image paths are referenced in post content or meta fields.
- Making sure no plugin settings will break after replacement.
- Confirming that serialized arrays (like widget settings) are handled properly.
Using --skip-columns
and --include-columns
Wisely
Sometimes you don't want to replace everything in the database. For example, if you're updating a URL but don't want to touch user emails or comment content, you can skip certain columns:
wp search-replace 'old-url.com' 'new-url.com' --skip-columns=comment_content,user_email
Alternatively, if you only want to update specific tables or columns:
wp search-replace 'old-url.com' 'new-url.com' wp_posts wp_postmeta --include-columns=post_content
This kind of precision helps prevent unwanted side effects, especially when dealing with large sites or custom databases.
Handling SSL and Case Sensitivity
If you're switching from HTTP to HTTPS:
wp search-replace 'http://example.com' 'https://example.com'
This updates all instances of the non-secure version of your site to the secure one.
Also, by default, search-replace
is case-sensitive. If you want to ignore case:
wp search-replace 'OldString' 'NewString' --case-insensitive
Just be careful — this might lead to more replacements than expected if similar strings exist in different cases.
That's the main idea behind using search-replace
with WP-CLI. It's straightforward once you get the hang of it, but it pays to be cautious. The flexibility it offers make it a go-to tool for migrations, cleanups, and batch edits in WordPress databases.
The above is the detailed content of How to search and replace in the database with WP-CLI. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website

When developing Gutenberg blocks, the correct method of enqueue assets includes: 1. Use register_block_type to specify the paths of editor_script, editor_style and style; 2. Register resources through wp_register_script and wp_register_style in functions.php or plug-in, and set the correct dependencies and versions; 3. Configure the build tool to output the appropriate module format and ensure that the path is consistent; 4. Control the loading logic of the front-end style through add_theme_support or enqueue_block_assets to ensure that the loading logic of the front-end style is ensured.

To add custom user fields, you need to select the extension method according to the platform and pay attention to data verification and permission control. Common practices include: 1. Use additional tables or key-value pairs of the database to store information; 2. Add input boxes to the front end and integrate with the back end; 3. Constrain format checks and access permissions for sensitive data; 4. Update interfaces and templates to support new field display and editing, while taking into account mobile adaptation and user experience.

robots.txt is crucial to the SEO of WordPress websites, and can guide search engines to crawl behavior, avoid duplicate content and improve efficiency. 1. Block system paths such as /wp-admin/ and /wp-includes/, but avoid accidentally blocking the /uploads/ directory; 2. Add Sitemap paths such as Sitemap: https://yourdomain.com/sitemap.xml to help search engines quickly discover site maps; 3. Limit /page/ and URLs with parameters to reduce crawler waste, but be careful not to block important archive pages; 4. Avoid common mistakes such as accidentally blocking the entire site, cache plug-in affecting updates, and ignoring the matching of mobile terminals and subdomains.
