Back to Community
Home / Community / Core → Alpha/beta/rc

Troubleshooting Common WordPress Multisite Issues in Beta Releases

25 threads Sep 7, 2025 Core → Alpha/beta/rc

Content

Running a WordPress Multisite network on a beta release can be a powerful way to test new features, but it can also introduce unique challenges. Based on community reports from various beta cycles, this guide covers the most common Multisite problems and their solutions.

1. The "Revisions" Meta Box is Missing on Sub-Sites

The Problem: Sub-site administrators report that the Revisions checkbox is missing from their Screen Options, preventing them from tracking post changes.

The Solution: This is often not a bug. In newer versions of WordPress, the Revisions meta box only becomes available after a post or page has been saved or published for the first time. This is a change from older behavior where autosaves would generate revisions during editing. Check the Screen Options tab again after the initial publish.

2. "Are you sure you want to do this?" Error When Creating a Site

The Problem: When attempting to add a new site to a network, the process fails with a non-specific permissions error.

The Solution: This error is often related to server configuration, not the beta software itself. Common causes include:

  • SSL and Complex Paths: Running Multisite in a subdirectory on an SSL domain (e.g., https://sub.domain.com/path/) can sometimes conflict. Ensure your server's SSL certificate is valid for all subdomains if using subdomain installs.
  • .htaccess Rules: An incorrect .htaccess file is a frequent culprit. If you upgraded from an older version like 3.4.2, try copying the Multisite rules from that version's .htaccess into your new one. The official WordPress .htaccess documentation provides the correct rules to use.
  • Mod_Security: Some hosting providers have aggressive Mod_Security rules that can block site creation requests. Contact your host to check if this is the case.

3. Media Upload Paths Disappear or Don't Change

The Problem: The option to set a custom upload path (wp-admin/options-media.php) is missing on fresh installs. Furthermore, when using the switch_to_blog() function, the wp_upload_dir() path may not update correctly when switching from the main site.

The Solution: The removal of the UI for the upload path was an intentional change. The system now uses a predefined directory structure. If you must change it, you can manually add the upload_path record to the site's wp_options table in the database. After adding any value, the option will reappear in the media settings screen. The switch_to_blog() issue is a known bug that was tracked and resolved in a Trac ticket.

4. Network Admin Dashboard Shows Incorrect Counts

The Problem: The "Right Now" widget in the Network Admin displays "0 sites and 0 users" even though sites and users exist.

The Solution: This is a known bug that sometimes appears in beta releases. It is often related to how user roles and spam statuses are counted. The counts are typically corrected in subsequent releases. You can safely ignore this visual bug, as it does not affect functionality.

5. Unable to Access Sub-Site Dashboards (403 Forbidden)

The Problem: After creating a new site, accessing its dashboard returns a 403 Access Forbidden error.

The Solution: This is almost always a server permissions or rewrite issue.

  • Ensure mod_rewrite is enabled on your Apache server.
  • Verify that your .htaccess file contains the correct Multisite rewrite rules.
  • Check that file permissions for the WordPress directory and wp-content/blogs.dir (for older networks) are writable by the server. For networks created in WordPress 3.5 and later, the blogs.dir directory is no longer used; uploads are stored in wp-content/uploads/sites/[site-id]/.

General Beta Testing Best Practices for Multisite

  • Always Use a Staging Environment: Never run beta software on a live production network.
  • Check Trac Tickets: Many reported issues already have a ticket on WordPress Core Trac. Searching for or creating a ticket is the most effective way to get a bug addressed by the WordPress core development team.
  • Disable Plugins: Before reporting a bug, disable all plugins to confirm the issue is with the core software and not a compatibility problem.
  • Clear Cookies and Cache: Many strange login and redirect issues are resolved by completely clearing your browser's cookies and cache for the site.

By understanding these common pitfalls, you can confidently test WordPress Multisite beta releases and contribute valuable feedback to the community.

Related Support Threads Support