WordPress MU

I have just installed wordpress mu on a SuSE Enterprise box and every time someone creates a new blog and tries to visit it, they get a 404 error. I am wondering how wpmu handles url creation. I believe that everything just goes into a database and there is nothing actually written to the file system. is this correct? If not, where should it be creating new directories, files, etc?

that's correct, it's all in the database.

Seems you missed quite a few steps from the readme though.
Did you enable the wildcard subdomains?
is mod rewriten enabled and working properly?

I know mod_rewrite is working properly. I didn't think I needed to enable wildcard domains because I am using the directory structure and not the subdomain structure.

This may be part of the problem:

2. In the <Directory> directive of your virtual host, look for this line
"AllowOverride None"
and change it to
"AllowOverride FileInfo Options"

http://trac.mu.wordpress.org/browser/trunk/README.txt#L21

I have done that as well. I have done everything it says in the readme file except for the DNS setup because I have been told I don't need it if I am using the directory url structure as opposed to the subdomain structure.

Got a link?

anyone please? I still have the same problem.

I am sure the mod_rewrite is loaded, and I've set AllowOverride to "All"

but both the new post and new blog will direct to a 404 page.

please help!
thank you!

sorry, I am running wp-mu on apache 2.2.8, php 5.2.6 ,
the system is windows server 2003 enterprise edition sp2.

thank you !

the system is windows server 2003 enterprise edition sp2

In which case you do not have the same problem as the original poster was on Suse Linux.

But as I've never tried setting it up on windows, I've no idea beyond that.

My understanding is that apache on the windows platform does not have mod_rewrite built in and you actually have to purchase an addon to get it in there. I don't use the platform either but a quick search of the forums shows a couple of threads covering that.

Reviewing the webserver's error logs to determine what the specific error is would be the first step of debugging as noted in the debugging page linked to from the readme file.

Apache is Apache, in general. It had mod_rewrite on either platform.

IIS does not, however.

404 errors can also be triggered by a missing .htaccess file as well.

Hi, i have wordpress mu for months now & around 370 blogs working. Now, all deleted just 19 working to reduce load.

But, now every time someone creates a new blog and tries to visit it, they get a 404 error and redirect to hosting server's 404 page.

yes i have upgraded the wordpress around a month back.

But the error is increasing now a days. now even the previous sub-domain are not working.
Let me explain you the errors:

1. i noticed that my friends are registering the new sub-domain blogs but it doesn't work. my existing 19 blogs continued to work gr8.
2. then i noticed that i had configured the wp to create blogs at sub-domains but it is now creating sub-folders.
3. after few days i noticed error in installing a classifieds script at goelji.com/classifieds.
4. few days later my existing blogs on sub-domains started diverting to my main blog.

I think that upgrade has changed my .htaccess file. can some one provide me a file copy that works.

Look at htacces.dist in the file download. Compare it to yours.

hey ... ive got the same problem, ive just installed the latest wp mu and when new users register and ask for new blog, on the activation mail where they get http://newblog.mydomain.com/auiauidad564d564d when they hit the activation code they get 404 from server ... saying that http://newblog.mydomain.com does not exist :(((

where should i start ??

Did you create a blog from the backend and see if it works?

If not, you didn't do either the wildcard DNS record or the wildcard edit in Apache.

ok ... how do i create the wildcard dns record ?

It's in the readme.txt in the download.

Or ask your host to do it.

Name TTL Class Type Data
Built in A records
bestfrequency.com 86400 IN A 89.34.23.233 Click to remove
*.bestfrequency.com 86400 IN A 89.34.23.233 Click to remove
Restore default A records

ok ... do i have or have not a wildcard dns record ??

Yes, in those DNS records.

You also need to have it set up in Apache - on the server, in the httpd.conf file. As outlined in the readme.

that's not good, i don`t have access to that file :(( i must have a chip chat with my host provider