WordPress多站点：能否禁止新增站点创建约10张数据库表？

Great question! WordPress Multisite’s default behavior of spinning up a full set of wp_{blog_id}_* tables (like wp_2_posts, wp_2_comments) works well for data isolation, but I totally get why you’d want to bypass that as your network scales—even with InnoDB’s theoretical 4-billion table limit, managing thousands of separate tables gets messy and can hit performance bottlenecks down the line. Here are your actionable solutions:

1. Use a WordPress Hook to Block Table Creation #

WordPress has a built-in hook wpmu_create_tables that lets you intercept the default table-creation workflow. Add this code to your theme’s functions.php file or a custom plugin:

add_action('wpmu_create_tables', function($blog_id, $user_id, $domain, $path, $site_id, $meta) {
    // Kill the default table creation action before it runs
    remove_action('wpmu_create_tables', 'wpmu_create_tables');
}, 1);

Important caveat: This will completely stop new sites from getting their own tables, meaning all new sites will share the main site’s tables. That breaks data isolation—posts, comments, and metadata from different sites will live in the same tables. Only use this if you don’t need to keep site data separate.

2. Implement Shared Tables (Recommended) #

If you want to cut down on table count and keep data isolated, use a shared table architecture. This means multiple sites use the same core tables (like wp_posts, wp_comments) but are separated by the site_id or blog_id field.

You can customize table mappings using WordPress filters. Here’s a basic example to force certain tables to use the main site’s prefix:

add_filter('pre_get_table_charset', function($charset, $table) {
    // List tables you want to share across all sites
    $shared_tables = ['posts', 'comments', 'postmeta', 'commentmeta'];
    $main_prefix = $GLOBALS['wpdb']->base_prefix;

    foreach ($shared_tables as $tbl) {
        // Check if the table is one of our shared ones and not already using the main prefix
        if (str_contains($table, $tbl) && !str_starts_with($table, $main_prefix)) {
            // Override to use the main site's table instead of a site-specific one
            $GLOBALS['wpdb']->tables[$tbl] = $main_prefix . $tbl;
        }
    }
    return $charset;
}, 10, 2);

You’ll also need to ensure all queries automatically filter by blog_id to avoid mixing data. For example, add a filter to posts_where to include the current site’s ID in post queries. This requires some custom development, but it’s the best balance between reducing table count and maintaining data separation.

3. Modify Core Files (Not Recommended) #

You could directly edit the wpmu_create_tables function in wp-admin/includes/ms.php by commenting out the table-creation lines, but this is a bad idea. WordPress updates will overwrite your changes, and it makes your site harder to maintain and debug.

Key Notes #

• Backup first: Any change to your database structure risks data loss—always take a full backup before experimenting.
• Plan for existing sites: If you already have a large network, retrofitting shared tables is tricky. It’s easiest to set this up before creating most of your sites.
• Optimize queries: When using shared tables, add indexes on blog_id or site_id to keep query performance fast.

内容的提问来源于stack exchange，提问作者Heopas