How to migrate a multisite site to a single site
To migrate subsites in WordPress multi-site to a single site, you need to perform the following steps in turn: 1. Use WordPress's own export tool to export articles, pages, etc.; 2. Export the table with the corresponding prefix from the database and rename it to a single-site format, while replacing the old domain name; 3. Manually migrate media files and repair paths; 4. Configure the themes, plug-ins and settings of the new site and conduct testing. The entire process requires attention to data cleaning, URL replacement and plug-in compatibility to ensure normal functions after migration.
Migrating a subsite in a WordPress multisite to a single site is actually a relatively common but operational care. Because the data structure of multi-site is slightly different from that of single-site, there may be problems with copying files or databases directly. The focus is on extracting the data of the target substation and rebuilding it correctly in the new environment.
Here are some key steps and precautions to help you complete the migration smoothly.
1. Export subsite content
WordPress's own "Export" tool (Tools > Export) can be used to export articles, pages, comments, custom fields and other content. While it can't export everything (like theme settings, plugin data, etc.), it's enough for basic content migration.
- Log in to the backend of the subsite you want to migrate
- Go to Tools > Export
- Select "All" or select a specific content type as needed
- Download the generated
.xml
file
This method is suitable for migrating basic content such as articles, pages, media libraries, etc. If your theme or plugin depends on a lot of settings, it may need to be handled manually.
2. Export and organize the database
Each subsite in a multi-site has its own prefix table (such as wp_2_posts
, wp_2_options
, etc.). To migrate this data to a single site environment, you need:
- Use phpMyAdmin or other database management tools
- Find the database table for the corresponding subsite (for example, start with
wp_2_
) - Export data from these tables
- Change the table name to a single site format (such as
wp_posts
,wp_options
)
It should be noted that it is best to clean up unnecessary data before importing, such as temporary options, logging, etc. Also, make sure to replace the old domain name information, otherwise the link will point to the original multi-site address.
You can use SQL replacement statements to update the URL:
UPDATE wp_options SET option_value = replace(option_value, 'http://oldsite.com', 'http://newsite.com') WHERE option_name = 'home' OR option_name = 'siteurl';
3. Migrate media files and other resources
When exporting XML, you can choose whether to include attachments, but sometimes it fails or misses. A safer way is:
- Copy files directly from
/wp-content/uploads/sites/2/
of the server - Paste in new single site
/wp-content/uploads/
path - Then update the GUID and file path through the "Media Library Repair Plugin" or SQL
This ensures that the pictures, videos and other resources can be displayed normally.
4. Set up a new site environment
After the migration is complete, don't forget to adjust some key settings for the new site:
- Check if the permalinks settings are consistent
- Replace the appropriate theme and restore the appearance settings
- Install the necessary plug-ins and import relevant configurations
- Test whether the front desk and background functions are normal
Some plug-ins will use different loading methods in multi-site environments, and may fail after migration to a single site. At this time, you need to reconfigure or replace the plug-in.
Basically that's it. The whole process is not too complicated, but details are easy to ignore, such as incomplete URL replacement, permission issues, or some plug-in dependencies are not handled. As long as you take it step by step, most situations can be solved smoothly.
The above is the detailed content of How to migrate a multisite site to a single site. 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 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.

The key to adding custom rewrite rules in WordPress is to use the add_rewrite_rule function and make sure the rules take effect correctly. 1. Use add_rewrite_rule to register the rule, the format is add_rewrite_rule($regex,$redirect,$after), where $regex is a regular expression matching URL, $redirect specifies the actual query, and $after controls the rule location; 2. Custom query variables need to be added through add_filter; 3. After modification, the fixed link settings must be refreshed; 4. It is recommended to place the rule in 'top' to avoid conflicts; 5. You can use the plug-in to view the current rule for convenience

WordPressrequiresatleastPHP7.4,thoughusing8.0orhigherisrecommendedforbetterperformanceandsecurity.Olderversionslike5.6areoutdated,unsupported,andposesecurityrisks.UsingupdatedPHPimprovessecurity,enhancesperformance,andensurescompatibilitywithmodernpl

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.

To properly introduce style files in WordPress themes or plugins, you should use the wp_enqueue_style() function. 1. Use wp_enqueue_style() to register and load the CSS file. The basic structure is wp_enqueue_style($handle,$src,$deps,$ver,$media), where $handle is a unique identifier, $src is the CSS file URL, $deps is the dependency style, $ver is the version number, and $media is the media type; 2. By placing the enqueue operation in the functions.php file and using wp_enqueue_script

InspectorControls is a component used in Gutenberg development to add custom controls in the right sidebar. 1. It belongs to the @wordpress/block-editor package. 2. It is often used with PanelBody, TextControl and other components. 3. When using it, you need to introduce and reasonably lay out control types such as text boxes, pull-down selections, switches, sliders and color selectors in edit.js. 4. Pay attention to grouping settings, keep them simple, support internationalization and optimize performance.

It is not complicated to add security response headers in WordPress, and can be implemented through server configuration, security plug-ins, or CDN. 1. Add header information such as X-Content-Type-Options, X-Frame-Options, etc. through Apache or Nginx configuration files; 2. Use plug-ins such as Wordfence and iThemesSecurity to simplify settings; 3. Use the built-in functions of CDN platforms such as Cloudflare to configure global header information. After configuration, you should use SecurityHeaders.com or ChromeDevTools to test and verify to ensure correctness and get at least A-level scores, while paying attention to backup and understanding the enabled
