WordPress MU

I've got a 1.5.1-based site at Red Hat that's showing some weirdness... when I try to visit a post on the main blog, like:

http://foo.bar.com/wordpress-mu/2008/07/02/bretm-test/

Wordpress-MU does some funky things in wpmu-settings.php... specifically:

1) $current_site exists
2) $current_blog does not
3) $domain is correct
4) $path is correct (/wordpress-mu/)
5) $blogname is wrong (2008)

I'm not sure if this is an actual code bug that only reveals itself when NOBLOGREDIRECT is set, or if it's due to flawed config/flawed db values.

Thoughts?

You should upate your server to mu svn or the release candidate I mentioned a few days ago: http://mu.wordpress.org/forums/topic.php?id=8885

I changed the behaviour of the redirect. If you don't set NOBLOGREDIRECT it won't redirect to the signup form.

Do you have VHOST set to yes or no?

1) your RC is on my list to rebase to, I'll certainly test under that once I have pkgs... but looking at the diff, I don't see anything in there that'd fix my issue.

2) VHOST is set to no.

3) I do want a redirect when someone visits an invalid link. But in this case, WPMU is mistaking a perfectly valid posting link:

http://foo.com/wordpress-mu/2008/07/11/baz-buzz-blah

for a blog called "2008" that doesn't exist.

4) I'm trying a work-around by creating a new blog, /wordpress-mu/workaround/, imnporting all the data there, and then perhaps have an internal RewriteRule on /wordpress-mu/(\d\d\d\d) --> /wordpress-mu/workaround/$1

That should get me unblocked for a bit until we can figure this out.

There should be "blog" in there before "/2008" AFAIR. The url should be http://foo.com/wordpress-mu/blog/2008/07/11/baz-buzz-blah because of this very reason.

Did you change a VHOST=yes site to VHOST=no by any chance? The "/blog" doesn't appear with VHOST on.

[root@devfu-test wordpress-mu]# cat wp-config.php |grep VHOST
define('VHOST', 'no');
[root@devfu-test wordpress-mu]#

Where does that "blog" bit come from? wpmu-settings.php, or in the db as a part of creation of the first blog?

It should be there when you installed MU. It's strange to see it gone!

More than likely, it's do to how we provisioned the db... I'll check our templating system, it's entirely possible we took a bad snapshot.