This is no longer in beta, so the "NOTE: This Feature is currently in Beta" box can be removed, right? This would be my first edit, so I'd like some input before I do it. Dholowiski 17:06, 18 June 2010 (UTC)
Makes sense to me. Go for it. mrmist 17:16, 18 June 2010 (UTC)
So I checked to see if I could successfully set up a multisite and it seemed to turn out okay, all except a crucial glitch probably caused by the lack of an pre-existing .htaccess file prior to install. I can still run WordPress just fine though, so what if I want to reverse my changes, now what?
I would assume it's just a matter of deleting the same lines that I added, but some extra words on it in the codex page would certainly put my mind more at ease.
I think it should be on a separate page. It's about half as long as the install (to remove it completely) and on a separate page can be found by those who have done the network creation then changed their minds later. I can see it being overwhelming if the entire process was listed on this page as well. A link to it, yes.
It might be worth noting somewhere, that with certain autoinstalls (at least my Dreamhost autoinstall) will not create a wp-config.php file identical to the one you get with a WordPress installed manually.
Before applying multi-site, though having installed BuddyPress and several other plugins (I don't know if that could affect it), my wp-config.php looked like this:
<?php
/** WordPress's config file **/
/** http://wordpress.org/ **/
// ** MySQL settings ** // define('WP_CACHE', true); //Added by WP-Cache Manager define('DB_NAME', 'itsname'); // The name of the database define('DB_USER', 'myname'); // Your MySQL username define('DB_PASSWORD', 'password'); // ...and password define('DB_HOST', 'mysql.mydomain.dreamhosters.com'); // ...and the server MySQL is running on
// Change the prefix if you want to have multiple blogs in a single database.
$table_prefix = 'wp_2hfdag_'; // example: 'wp_' or 'b2' or 'mylogin_'
// Turning off Post Revisions. Comment this line out if you would like them to be on.
define('WP_POST_REVISIONS', false );
// Change this to localize WordPress. A corresponding MO file for the // chosen language must be installed to wp-includes/languages. // For example, install de.mo to wp-includes/languages and set WPLANG to 'de' // to enable German language support. define ('WPLANG', );
/* Stop editing */
$server = DB_HOST; $loginsql = DB_USER; $passsql = DB_PASSWORD; $base = DB_NAME;
define('ABSPATH', dirname(__FILE__).'/');
// Get everything else require_once(ABSPATH.'wp-settings.php'); ?>
I had a need to server multiple subdomains without a shared DocumentRoot. So I did the following -
The main installation is at http://domain.com/weblog
I do not follow the codex to the letter and create a virtual directory section without a wildcard. Now I have a subdomain http://user1.domain.com/ that does not hare the document root with the main WP installation.
To get WP working:
1. Create a symbolic link in the DocumentRoot of user1.domain.com to the installation directory.
2. Place the following .htaccess file in the document root of user1.domain.com
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_METHOD} POST
RewriteRule ^wp-admin(.*)$ weblog/wp-admin$1 [R=307,L]
RewriteRule ^wp-admin(.*)$ weblog/wp-admin$1 [R=301,L]
RewriteRule ^(.*)$ /weblog/$1 [L]
This does create a problem when the POST method is used. A simple 301 redirect seems to be dropping the post variables. So, I had to create a 307 redirect which pops up a dialog box prompting the user to resubmit the data. I am not a rewrite expert. But I think an expert could fix this. The problem was faced particularly in the `wp-admin/nav-menus.php` where new menus were not being created due to the dropped POST information.
Would someone like to comment on if this should go into the Codex?
- Bharath Bhushan Lohray 11:36 2011-05-26
I found this article confusing, and from what I have read in the forum I am not alone, so I plan to try and make it a little clearer. I think eventually it should be split up, because no one really needs to read all of it, and it is irritating to read through a lot of complex information that you later discover you didn't need. But initially I'll just try to fix two issues: adding the promised but missing information to "help you to decide if you really need a multi-site install", and making it clear that you can use multisite with end-user registration of new sites turned off.
Rod Whiteley 11:48, 30 December 2011 (UTC)