WordPress MU

wp_blogs is a database table. Look out for phpmyadmin which makes it easy to admin the database. Use Google to find out more about mysql/phpmyadmin/Cpanel/whatever you use to admin your site.

yes, i use phpmyadmin but i haven't this table in my database...i have nine tables for the initial installation and others nine tables for each blog added ..... i had installed wordpress mu stable 1.5.1.3....what is the problem? thank you very much donncha for your answers ;)

Try the unstable version.. it's getting all the attention right now!

where can i find the unstable version? tnk

Unstable is here:

http://mu.wordpress.org/nightly-builds/

* wpmu-unstable.zip
* wpmu-unstable.tar.gz

Donncha - We really need to add some doco and somebody needs to go and remove a few little bugs from the "stable" version.
#1 There are no instructions telling people to go to wp-inst/wp-newblog.php. That's why everybody get's this error.
#2 In index.php the code that checks the file permissions is incorrect and throws up an error when the files have the correct permissions. This might have been fixed in the unstable version. I think someone needs to create a new stable version.

yes true i have this error...i get to wp-newblog.php but the webserver redirect me to blog home....why? thank

bazcewel - I think I need to need to get rid of the stable version. it's a dead duck anyway as the differences between it and the unstable version are significant!

there is a solution for the problem ? when i go to http://www.sito.it/wpmu/wp-inst/wp-newblog.php script redirect me to http://www.sito.it/wpmu/ why? how can i resolve? thanks again for your very importanti help !

Hi.

I installed the stable WPMU branch last night on a TextDrive server and ran into the same issue: "ERROR - Sorry, this blog doesn't exist. Try the homepage instead!" The install process allowed me to enter the admin interface and post. The posts got correctly databased but never made it out to a weblog. Also, the confirmation mail I received contained a URL that wouldn't let me log in because, well -- sorry, this blog didn't exist.

Today I dropped the whole install and tried again from scratch using 2005-08-08 build.

Worse. This time I couldn't even log into the admin interface:

Fatal Error
Could Not Find Blog!
Searched for domain.tld/dir/ in db_name::wp_blogs table. Is that right?
Please check that your database contains the following tables:

* wp_blogs
* wp_users
* wp_usermeta
* wp_site
* wp_sitemeta
* wp_sitecategories

If you suspect a problem please report it to support forums!

Yes, all the database tables got created and populated correctly.

In the confirmation mail I got URLs that returned nothing but four-oh-fours. Note the funny doubling of the directory in which I installed the app:

Dear User,

Your new WordPress.com blog has been successfully set up at:
http://domain.tld/dir/dir

You can log in to the administrator account with the following information:
Username: admin
Password: xxxxxx
Login Here: http://domain.tld/dir/dirwp-login.php

We hope you enjoy your new weblog.
Thanks!

--The WordPress Team
http://www.wordpress.com/

Any thoughts?

scuse me...anyone know a solution for my problem? tnk

now wp_newblog.php run perfectly but i must write http://www.site.it/wpmu/wpmu/... and non http://www.site.it/wpmu/....... and when i create a new blog ..server say "error 404" to url of new blog ! .....why all these preblems? tnk

I'm using WPMU unstable and and ran into the same issue: "ERROR - Sorry, this blog doesn't exist. Try the homepage instead!"
I don't know the solution :(

ferocious go in the sql table "wp_blogs" and where the path is for example /wpmu , add a slash so /wpmu/ bye

Thanks, Ste_000 -- that helped, up to a point: I managed to log in and post.

The paths are still weird. Most links now point to domain.tld/dir/dir/whatever; some of them work, others don't. The Home link to domain.tld/dir/dir, for instance, fails, whereas the archived article links to domain.tld/dir/dir/etc work.

I added another trailing slash to the path specified in the wp_site table, to no avail.