Take the 2-minute tour ×
WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

I've been looking into setting up a WordPress network install. Everything has been going pretty smoothly until I get to the point where my desired domain layout doesn't fit well.

I would like to have a layout as follows:

blog.*.stackexchange.com

so for example, I would like to have multiple sites in a network that look like:

blog.wordpress.stackexchange.com
blog.apple.stackexchange.com
blog.$site.stackexchange.com

I think I could get this working with some creative re-write rules, and manual DNS intervention but I'd rather have a setup where I can hand off the creation of everything but the DNS to someone else (we already have a process for automatically creating all sub-domains needed in DNS)

From my playing around and reading WP really wants the sites to be the next level domain, so in my above example, it wants the main WP blog to be at stackexchange.com and the network blogs to be at wordpress.stackexchange.com.

Is there any way to achieve my desired effect or should I just go the route of doing blog.stackexchange.com/$site ?

share|improve this question
2  
I'm pretty sure you're going to have to use creative re-write rules and manual DNS intervention. I'm also pretty sure this is by-design so that you can't hand off the creation of everything but the DNS to <del>me</del><ins>someone else</ins>... whistles </sarcasm> (: –  Rebecca Chernoff Mar 18 '11 at 4:49
    
I've added a bounty in the hope that someone comes along with a nice step by step guide so Zypher can spend more time worrying about keeping SE up and less time looking into community blogs. –  Thomas McDonald Mar 20 '11 at 20:54
add comment

2 Answers 2

up vote 2 down vote accepted
+150

You could use the Domain Mapper plugin for this. Drawback being that you'd have manually configure each subblog.

share|improve this answer
    
Interesting, does it do a redirect or just serve the content? I guess what i'm trying to ask is does the address bar change for the end user? –  Zypher Mar 18 '11 at 17:25
    
@Zypher No, it just serves the content. –  Thomas McDonald Mar 18 '11 at 17:27
1  
Tutorial for use the plugin: ottopress.com/2010/… Important: it is without problems, when you install WP and active the plugin and after this import data or moigrate system; it si not so easy to add this plugin after the blog has a life before domain mapping. it give also other plugins to make the work in wp backend a little bid easier. wordpress.org/extend/plugins/networks-for-wordpress –  bueltge Mar 21 '11 at 15:36
    
due to lack of alternative, have +150 rep. –  Thomas McDonald Mar 26 '11 at 20:03
    
that's nice, thanks! –  Wietse Venema Mar 30 '11 at 6:36
add comment

You could do this with a customized sunrise.php file. This is essentially how the domain mapping plugin works, however it puts a pretty front end on it. For something custom, you can write some simple PHP to do basically the same thing.

The essence of multisite involves figuring out what site to serve. The Domain mapping plugin does this by creating a wp_domain_mapping table, and storing the information in there. Thus when it gets a request for xxx.com, it looks in that table and sees that that corresponds to blog_id 123.

First, make a WordPress setup, and make it multisite. Doesn't matter where it really lives, because we're going to change all that. For simplicity, I'd put it at blog.stackexchange.com and make it a subdirectory type site (those are easier). The subdirectories created would likely be the slugs. /wordpress, /apple, /whatever.

So yes, to start with, you are indeed making it live at blog.stackexchange.com/wordpress. Consider this your staging environment. When you create each site, you can do stuff to it here until you decide to turn on the mapping.

To do domain mapping yourself, without the plugin, you'd do something like this:

Step one: add define( 'SUNRISE', 'on' ); to the top of your wp-config.php file.

Step two: create a sunrise.php file in the wp-content directory. Put <?php at the top to start with.

Step three: In the sunrise.php file is going to be your logic for determining what site to load.

You're going to base this on the $_SERVER[ 'HTTP_HOST' ] variable. How you do that exactly is easy: however you want to do it. If you want to just write a regex to look for '/blog\.(.*)\.stackexchange\.com/' and then look for that bit in the database, you can do that.

Since you're using the same slug here as the "subdirectory", you don't need a separate table. You can just look in the main wp_blogs table to find the site you need. Something similar to this:

$current_blog = $wpdb->get_var( "SELECT blog_id FROM {$wpdb->blogs} WHERE path = '/wordpress/' LIMIT 1" );

Once you have the $current_blog, then you need the following code:

$current_blog->domain = $_SERVER[ 'HTTP_HOST' ];
$current_blog->path = '/';
$blog_id = $current_blog->blog_id;
$site_id = $current_blog->site_id;
$current_site = $wpdb->get_row( "SELECT * from {$wpdb->site} WHERE id = '{$current_blog->site_id}' LIMIT 0,1" );
$current_site->blog_id = $current_blog->blog_id;

This pre-defines the $current_blog and $current_site global variables instead of letting WordPress' MU functions do it.

This would be enough to get the site up and working (after getting your DNS to point to it and getting the virtual hosting stuff sorted out), however most of the static URLs used in the HTML code would still point to blog.stackexchange.com/wordpress, since that's where the site would really be. Also, the Canonical URL function would probably not like the URL and would redirect you too.

To remedy these problems, you'd also likely want to pre-define several of the URLs associated with the site. Things like WP_SITEURL and WP_HOME. Also, WP_CONTENT_URL, WP_PLUGIN_URL, and WPMU_PLUGIN_URL. That should cover most cases of the URLs being adjusted.

Finally, you'll want to set the 'COOKIE_DOMAIN'. Since you likely want logins to be shared across the whole of the thing, you can set it to stackexchange.com, or even higher if you don't want them to be shared logins.

If you want to talk about integrating the normal stackexchange login system into WordPress, I can answer questions on that too, but it would be a bit more detailed of an answer. :)

Feel free to email me if you want more help with this. Glad to assist: otto at wordpress.org.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.