While I'm quite capable of hacking the core to death, I'm wondering if this might be better suited for an install option instead.
When installing, it seems many people are using a subdomain for their primary install, but they would like to have the usernames be on the same level of subdomain as the primary. Mainly for incorporating into existing sites I suppose.
So, I'm wondering if it would be possible to allow an option in the install for the following:
1) specify the domain to be used overall (example.tld)
2) specify the primary MU site (primary.example.tld)
Then, during sign-up, a new blog is created as username.example.tld, instead of username.primary.example.tld as it is now.
What brought this up, and lead to a thorough search for me here, was I'm working on taking an existing site that's coming close to 5 years of age, and implementing MU as an added feature. While the main action of the original site is primarily a forum, I'd hate to have it all re-indexed by switching that to a sub-domain, to free up the main domain.
Not to mention the headache of all the redirects since MU will be on it's own separate box(es).
It looks from the set-up that it's already somewhat possible, but I'm still playing around with (and breaking) it.
It looks like all it needs to do is treat blog_id 1 as the primary, while pulling the domain from the _site table.
The "best" success I've had so far with this is changing the value in the _site table, which "does" partially work.
Only some of the links are broken, like wp-login, wp-signup, etc. Those could be hardcoded into the theme though as needed.
Has anyone found any workarounds to this perhaps? Preferably without major hacks to the corefiles?
If not, is it something that has been considered for future versions?
Something that wp-signup could reference, and in turn wpmu-functions could use for sign-up as well?
As a note to Donncha, I'd be happy to help with moving it forward and "earning my keep" so to speak.