Simple Domain Mapping without any Plugins (WordPress 3.0)

Yep. The domain mapping is really a user interface.

Edit those details in the backend is exactly the same as editing the database.

This is working for me so far… all sites work, can log in. I wonder if we’re missing something that will break horribly down the road 🙂

define( 'DOMAIN_CURRENT_SITE', $_SERVER['HTTP_HOST'] );

@teggen – yes, subdomains or subfolders, doesn’t matter.

Actually, I DO recommend using the plugin as the included sunrise.php files helps with letting WP know you have some mapped domains before the rest fires up.

I know this is an old thread, but my question is regarding using subfolders instead of subdomains.

Do you need to use a wildcard DNS if you’re only using subfolders? To me, it doesn’t seem logical, but I’m wanting to make sure.

I’m trying to follow all these instructions for getting different domains to work, but EVERYBODY uses a subdomain example and not a subfolder example and it’s confusing, plus it’s NOT working for me.

Here’s my domain: maindomain.com

Here’s what I did:
1. Installed the network for maindomain.com using Codex instructions.
2. Created a site using the Super Admin panel and filled it in as follows: maindomain.com/secondarydomain/ (secondarydomain is the name of the folder that my second site resides)
3. Clicked edit for the “secondarydomain” site that I just created.
4. Changed the domain settings from “maindomain.com” to “secondarydomain.com” and change the path from “secondarydomain” to “/”.
5. Unchecked the “Update siteurl and home as well” box and filled those values in manually as “secondarydomain.com”.
6. Updated the “Fileupload Url” from “maindomain.com/secondarydomain/files” to “secondarydomain.com/files”.
7. Clicked “Update Settings”.
8. Attempted to log by using “secondarydomain.com/wp-admin” and instead of taking me there, it gives me a Forbidden 403 error. Where it gets weird is that the URL box switches from “secondarydomain.com/wp-admin/” to “secondarydomain.com/secondarydomain/wp-admin/” which makes NO sense. Also, if I manually type “maindomain.com/secondary/wp-admin/”, it does allow me to see the administrative area of “secondarydomain.com”.
9. I thought that the fix might be to change the ‘define(‘DOMAIN_CURRENT_SITE’…) line to what was recommended by chrisbrocklesby, but that had no effect.

Can anybody help me with this?

Sorry it took so long for me to get back on this post, but my issue was caused by me forgetting to add a line from the code that needs to go into your wp-config.php file.

From the codex, make sure to follow these steps exactly:

0. First, back up your existing wp-config.php and .htaccess files. 1. Create a blogs.dir directory under /wp-content/ This directory is used to stored uploaded media for your additional sites and must be writable by the web server. They should be CHOWNed and CHMODed the same as your wp-content directory.
2. Add the extra lines your WordPress installation generates into your wp-config.php file. These lines are dynamically generated for you based on your configuration. Edit the wp-config.php file while you are logged in to your sites admin panel. Paste the generated lines immediately above /* That’s all, stop editing! Happy blogging. */.
3. Add the generated mod_rewrite rules to your .htaccess file, replacing other WordPress rules. (If there isn’t one, then create it.) These lines are dynamically generated for you based on your configuration.
4. Log in again. Once the above steps are completed and the new wp-config.php & .htaccess files are saved, your network is enabled and configured. You will have to log in again. click “Log In” to refresh your Adminstration Panel. If you have problems logging back in, please clear your browser’s cache and cookies.