lunabyteI didn't notice this on trac so if it's buried there somewhere, forgive me.
This might get long, bear with me...
So I'm playing around on a domain, complete root install, subdomains, everything like it should be.
So I export some posts from an existing blog, and import them. OK, not too bad. Although I did notice that I had to go in an unjack pages, as they were set in the database as static (should be published), and the type wasn't set to page. This may be MU specific, or maybe what's coming down the pipe in WP 2.1. That's neither here nor there, but in case someone runs into it, you'll have to edit the posts table directly.
Back on track.
So I mirror my permalinks settings on the original blog, and check pages. Not a problem, although I did have to fix a couple of page slugs.
Now the kicker... posts.
As I'm sure you can guess, they failed. Similar to recent inquiries from a few people where they couldn't get /blog/ out of their post permalinks, where it wasn't a subdirectory install, and they were using subdomains.
Attempting to access a post without /blog/permalink/settings/ was kicking it's butt, and it kept trying to register the category. (Permalink structure is /%category%/%postname%/, fyi. Nothing special there)
So, here I am thinking it's something "special" to MU, and perhaps it "has" to be there. Well, it does. But, only for a NON vhost (I.E. subdirectories) install.
In wpmu-settings.php, on/about line 69 (1.0 release), it checks for vhost to be defined as yes. If so, no problem. If not, then it assumes a subdirectory install, and looks for certain things in the path to begin setting up the pulling of the content.
Now, for the problem. It's a vhost install, yet when wp-settings.php was created, it was defined as blank ( define('VHOST', '') ).
So, I manually change it to yes and all was well.
So, if someone does a vhost install (I.E. subdomains), which is the recommended method, shouldn't this be defined as yes/true when wp-settings is written?
Has anyone else ran into this?
