My suggestion is: use the same standard .htaccess configuration for WordPress on a single domain in each WordPress directory. <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> Along with it, add a small CODE to make sure users are redirected to the … Read more
Apparantly this happens with the newer version of domain mapping because sunrise.php itself needs to be updated. To solve it I: Copy the new sunrise.php file from wp-content/plugins/wordpress-mu-domain-mapping/sunrise.php to wp-content/sunrise.php and you’ll be fine. And it works now.
“example2.com sub1.example2com” Actually for subsites off of mapped sites, you want a multi network plugin. Free – http://wordpress.org/extend/plugins/wp-multi-network/ Paid – http://wpebooks.com/networks/
Shortly after, I was able to find Otto’s tutorial on the topic. WordPress 3.0: Multisite Domain Mapping Tutorial
There’s a pretty good step by step on moving WordPress in the Codex. It is what I follow when changing domains. Moving the files is pretty straight-forward. It is the hard-coded references in the database that are tricky. However, serialized search and replace will take care of all database changes. I’ve used the Velvet Blues … Read more
If you’re willing to create a child theme and put your PHP files in there, this approach is relatively clean. For each file, create a rewrite rule where you specify the path you want to use and the filename that should load. In the example below, /custom-path/ loads custom-file.php from the root of your child … Read more
Using “cookieless” domain for serving static assets is common recommendation performance tools give. The reasoning being that cookies do nothing at all for such files, but still consume resources. It is, however, not something WP can handle for following reasons: WordPress does not control domain. DNS points domain to specific server’s IP address, where WP … Read more
I recommend handling the 301 redirect in your web server rather than in WordPress. mod_rewrite or RedirectMatch will be much more efficient than spinning up WordPress to deliver a Location: header. <VirtualHost *:80> ServerName busted-cheap-url.com # mod_alias RedirectMatch permanent (.*) http://great-new-url.com$1 # OR mod_rewrite RewriteEngine on RewriteRule (.*) http://great-new-url.com$1 [R=301] </VirtualHost> There are several methods … Read more
Set server_name to the IP address, eg: server { listen 80; server_name 0.1.2.3; // other stuff } You could also leave it out, because the default in ngninx is an empty string. But then all those pieces in WordPress that don’t validate $_SERVER[‘SERVER_NAME’] and similar values … will just break. See ticket #25239 for the … Read more
Domain Mapping via Core You don’t need to use the domain mapping plugin if you are planning on running a WordPress Multisite with top-level domains and/or sudomains. WordPress allows you to change a sub-domain to a top level domain once you have added the site settings, see the screenshot below. Core works perfectly without Alias, … Read more