I've just tagged version 1, release candidate 1 in SVN. It's available for download here:
Please report problems using Trac and remember to select "WPMU 1.0" as your milestone.
Include the following in the description of the problem:
I've just tagged version 1, release candidate 1 in SVN. It's available for download here:
Please report problems using Trac and remember to select "WPMU 1.0" as your milestone.
Include the following in the description of the problem:
woot ! champagne !
Finally... Welcome WPMU v1.0!!!!!!!!!
Does this sound a bit rushed to anyone else too? Have many people tested out the new code, with the new file structure on their live sites?
I've upgraded my Blogs with the old file structure now with RC-1 and all went well, no problems.
Thanks to all developers, WPMU grows up very fast :D
"release candidate", it's not version 1.0 just yet. The more that test it the better it'll be!
*yay!*
kudos to all the WPMU devs
amanzi,
I know I have been testing it. There is NO WAY I would use this on a large site. I have three users and they are all me. I have tried out most of the mundane things I think people will do and I am upgrading as fast as donncha can check things in, which is pretty fast. I think we just need a lot of us to start from scratch testing vhost and non-vhost, go through all the normal kinds of things, and report things in trac. As donncha says the more of us that do that the faster a 1.0 release will happen.
What is there right now has been pretty stable and a lot of things that weren't working for me in the old layout are now working.
Yoshi or donncha,
How did you upgrade? I will need to upgrade my production site eventually and need to know if it just a matter of moving the blogs directory to the new wp-content folder and running the upgrade script. The current version on the server is from December (I think).
Seems to be working fine so far, new install with vhosts no probs. A couple of plugins seem broken though, was using firstrss to post rss feeds in r585.
Apart from that in wp-signup.php when logged in I'm getting the http addresses doubling up for "Here are the blogs you already have:" in the form http://main domain/sub domain.
Still checking it out though.
I do not have TRAC access, so I will post the bugs here.
Clean Install of WPMU, Not Using "Vhosts", This is installed on a Domain at 1&1 Servers, Domain is Http://LittleShellTribalMembers.com. Set to accept "http://LittleShellTribalMembers.com/blogsite"
Configuration problems in the MySql Database:
1)wp_1_options/siteurl wrong Domain Name. Shows "http://com/LittleShellTribalMembers/" Had to change to "http://LittleShellTribalMembers.com/"
2)wp_1_options/home wrong Domain Name. Shows "http://com/LittleShellTribalMembers/" Had to change to "http://LittleShellTribalMembers.com/"
3)wp_1_options/fileupload_url wrong Domain Name. Shows "http://com/LittleShellTribalMembers/files" Had to change to "http://LittleShellTribalMembers.com/files"
4)(Default User 1) wp_users/user_url wrong Domain Name. Shows "http://com/LittleShellTribalMembers/" Had to change to "http://LittleShellTribalMembers.com/"
All Other entries in the Database have the Correct URL for the Site.. Only the above had to be changed manually using phpmyadmin control panel for the MySql file.
Once I made all the changes, the site works fine so far! Good Job!
Everything works good for me on a clean install!
Rudeseal,
If you can post here you can post in trac, the username and passwords are the same for this forum and trac.
Yes, I am interested in the upgrade too, as my main MU is the 28th April version. As wp-inst is no more valid, what do we have to do to successfully upgrade the entire site.
1. I know .htaccess and wp-config will be problemactic. I intend to edit them manually. Note: No more wp-inst in .htaccess to most lines.
2. I must move all the files down one level.
3. Run upgrade.php and then run upgrade in Dashboard (Site Admin)
A clean install didn't generate any problems so far. The .htaccess is soo sooo simple. Donncha what happen to the other lines?
I am burning to upgrade my main MU whn 1.0 is released.
I'm going to attempt an upgrade on the virtual copy of my live site. Will post back later with results...
This is how I upgraded:
Warning: fopen() [function.fopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /var/www/virtual/blogtown.co.nz/wpmu-2006-06-28/wp-admin/wpmu-upgrade-site.php on line 32
So that's where I am now, more testing later...
That's a dns error. Can you dump the hostname from line 32 into a file and verify that you can ping the same hostname from your server?
Actually - bigger problems than I first experienced. The .htaccess file isn't working for me. I'm getting 500 server errors and this is showing up in the error log:
[Wed Jun 28 23:02:40 2006] [alert] [client 192.168.112.30] /var/www/virtual/blogtown.co.nz/wpmu-2006-06-28/.htaccess: RewriteBase: argument is not a valid URL, referer: http://blogtown.co.nz/wp-admin/themes.php
This is Apache2 with PHP5 on Ubunut 6.06
@donncha - yes, you're right about the DNS record. I missed the wild card dns record on my test server. That's fixed now and I ran the upgrade again and somehow it deactivated all the blogs!?
I reactivated the blogs and ran the upgrade script again and that completed OK.
Of course the site isn't much good without the htaccess file - any ideas why that isn't working?
That was a problem with converting the "archived" field from an enum to a tinyint. I reversed this change a few minutes ago. The link below has sql for you to reactivate all blogs:
I'm way behind on all thing MU-related but as soon as I can test this out, I'll be sure to let you know. :)
The .htaccess problem:
http://trac.mu.wordpress.org/ticket/52
OK - so if you have WPMU installed in the root of your site, you change line 2 to the following:
RewriteBase /
Is that correct? That was the only issue preventing me from upgrading my production site. If that fixes it I'll upgrade over the weekend.
Yup. That's correct!