Posted 1 year ago #
I need to update a multi-user version of wordpress from its current version of 2.6.5 to the current 3.1.3 Multi Site incarnation.
What are the real steps I need to do to upgrade?
What is the next version to upgrade to? 2.7?
And after that?
When can I get to the place where I can use the auto-update?
Will my MySQL database be effected?
Could I install a 3.1.3 Multi Site installation from scratch, and then import the sites from the 2.6.5mu installation?
What problems should I look out for?
1) Read http://codex.wordpress.org/Upgrading_WPMU and upgrade MANUALLY to 2.9.2 incrementally. (2.6.5 -> 2.7 -> 2.9.2)
2) MANUALLY upgrade to 3.0 (read http://codex.wordpress.org/Upgrading_WPMU#2.9.x_to_3.0 especially)
2) Auto-Upgrade to 3.1.3
You should look out for http://codex.wordpress.org/Upgrading_WPMU#2.9.x_to_3.0 issues mostly.
Follow the steps Ipstenu gave you.
Could I install a 3.1.3 Multi Site installation from scratch, and then import the sites from the 2.6.5mu installation?
No. This will result in a multitude of problesm.
When wpmu was merged in to WordPRess, the developers went through a lot of code to make sure you could upgrade as outlined above.
BACKUP your database before you start. Major WP upgraded DO affect the db, even on single sites.
Posted 1 year ago #
Thank you both. … It seems that I have my work cut out for me. ...
Posted 1 year ago #
I was mistaken. ... My initial start version is 2.6.
Can I go from 2.6 to 2.7?, or do I have to go through the 2.6.5 step first?
Yeah, you can go 2.6 to 2.7 :)
Posted 1 year ago #
Hmm one more question. ... I am using wordpress2.6mu. ...
I cannot find a WordPress2.7mu archived Download.
In the steps quoted above, are the versions the same?
does wordpress2.7 = wordpress2.7mu
does wordpress2.9.2 = wordpress2.9.2mu
does wordpress3.0 = wordpress3.0mu
And if they are not equal, where do I find the mu archived versions?
I cannot find a WordPress2.7mu archived Download.
Scroll down.
http://wordpress.org/download/release-archive/ has them at the end under "MU Releases."
Posted 12 months ago #
When told to, Move your wp-config.php and .htaccess files to a temporary directory:
Since I am in Mac OS X, and have enabled my ability to see, copy, and move, hidden files in the finder, can I do that, or should I use the terminal commands?
Either way works :) if you can see 'em and move 'em in finder, that's perfectly fine.
Posted 12 months ago #
I apologize, but this is a little confusing for me.
2.6 to 2.7
Backup WPMU
Download WPMU and unpack it into a scratch directory:
e.g. ~/wordpress-mu/
I did this with no problem
Move your wp-config.php and .htaccess files to a temporary directory:
e.g. mkdir ~/temp ; mv ~/www/.htaccess ~/www/wp-config.php ~/temp
Remove all the files in your www directory:
e.g., rm ~/www/*
I also did this.
Copy the new files from your scratch wordpress-mu directory into your www directory:
e.g., cp ~/wordpress-mu/* ~/www
I did this, but got confused. ... This copies everything from the unpacked downloaded scratch 2.7. into my WWW folder.
Remove the wp-admin and wp-includes directories:
e.g., rm -rf ~/www/wp-admin ; rm -rf ~/www/wp-includes
Note: Be careful when using the rm command with the -rf flag!
??? This seems to tell me to remove two of the directories that I just put in the WWW folder from the unpacked downloaded scratch 2.7?
Copy the directories from your scratch wordpress-mu directory into your www directory:
e.g. cp -R ~/wordpress-mu/wp-admin ~/www ; cp -R ~/wordpress-mu/wp-includes ~/www
??? This seems to tell me to put exact copies from my scratch folder back into the WWW folder. ... ??? Where did I go wrong?
Copy the files wp-content/index.php and wp-content/blogs.php from your scratch wordpress-mu directory into your www directory:
e.g. cp ~/wordpress-mu/wp-content/index.php ~/www/wp-content ; cp ~/wordpress-mu/wp-content/blogs.php ~/www/wp-content
??? This also seems to tell me to put exact copies from my scratch folder back into the WWW folder. ... ??? Where did I go wrong?
Copy your wp-config.php and .htaccess files back from your temporary directory into your www directory:
e.g. cp ~/temp/.htaccess ~/temp/wp-config.php ~/www
I have not gotten here yet.
Just do it in a way that makes sense to you then.
The instructions above (I didn't write them) are trying to explain bit by bit about moving the files and the folders separately, from the zip files, into your live folder, bit by bit.
THe process is in removing everything and putting in new files & folders rather than overwriting, which isn't as clean.
Posted 12 months ago #
All said with a smile and a wink.
That is fine except that what I might think is right, would be wrong. … I just need to make this upgrade work. … ;-)
I just need to be clear. … If I remove my entire set of WWW files, leaving my WWW folder totally empty. … And them place in all the virgin files from the unpacked downloaded scratch 2.7 into the WWW folder. …
which files/folders from my original WWW folder should be put back into the, now virgin WWW folder?
Is this right? Are there more than these four files and two folders?
My original .htaccess file unchanged
My original wp-config.php file - as it was, them modified with the additions.
My original wp-content/index.php
My original wp-content/blogs.php
My original plugin folder
My original themes folder
Really what you want to do is REPLACE the wordPress CORE files with the ones you download. Over and over again. Until it's all caught up.
e.g. means 'For example' so it's not something that should be taken literally, and is meant to be adapted per site.
which files/folders from my original WWW folder should be put back into the, now virgin WWW folder?
.htaccess
wp-config.php
/wp-content (THE WHOLE THING)
That's it. The rest is what we want you to upgrade ;)
Posted 12 months ago #
I did that. … And I can see the front page, but when I try to login, I get this error.
Too many redirects occurred trying to open “http://community4health.com/wp-login.php?redirect_to=http%3A%2F%2Fcommunity4health.com%2Fwp-admin%2F”. This might occur if you open a page that is redirected to open another page which then is redirected to open the original page.
Posted 12 months ago #
Sorry. … I meant to say "Thank you." before I ran on about my next hurdle.
Heh. S'okay. Rename .htaccess to old.htaccess for a bit. See if that helps?
Posted 12 months ago #
.
I went to an empty site, cleared out the cache, quit the browser, Then
I renamed the .htaccess file to old.htaccess. … Did the same with .oldhtaccess and back to .htaccess
Now the error reported on all three iterations is just. …
Too many redirects occurred trying to open “http://community4health.com/wp-admin/”. This might occur if you open a page that is redirected to open another page which then is redirected to open the original page.
Posted 12 months ago #
Might that be a permissions problem?
Posted 12 months ago #
This link goes to a little unlisted video of my address bar, so you can see the several redirects that it goes through before failure.
I meant rename the file and KEEP it renamed. Not rename it, and then go back. What happened when you used old.htaccess?
Posted 12 months ago #
When I renamed the file to old.htaccess, nothing changed.
The behavior is the same. I get the exact set of multiple redirects as I get when the name is .htaccess.
I left it renamed that way, old.htaccess, all night. … The behavior is the same right now.
Thanks :) (FYI, the more 'extra' things you do without being explicitly specific for us makes it HARDER for us to keep track of what's been done. So document clearly and completely.)
Let's turn off all the plugins. Go in via FTP and rename the folder to old-plugins.
Posted 12 months ago #
.
Honestly, thank you for your help.
I renamed the plugins folder inside the WP-content folder to old-plugins.
result - no change.
---
Sorry for the previous thing where I changed the thing several times. I was trying to cover all bases of one file, in case of misscommunication. … I was only trying to say, that I did the exact same test for three versions of the file name, just in case.
Did you download 2.7-MU or 2.7 regular?
Posted 12 months ago #
I downloaded and am trying to install WordPress2.7mu.
I also followed the directions http://codex.wordpress.org/Upgrading_WPMU for making changes to the wp-config.php file are what I changed. …
Okay, what EXACTLY did you add in to your wp-config.php file?
Posted 12 months ago #
I made the changes in the "define" area, as per the instrunctions here. …
http://codex.wordpress.org/Upgrading_WPMU#2.6_to_2.7
These are the only changes made. … I did not delete anything, just added these.
define('DOMAIN_CURRENT_SITE', 'community4health.tld');
define('PATH_CURRENT_SITE', '/');
define('BLOGID_CURRENT_SITE', '1');
define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');
define('NONCE_KEY', 'uniquestringfour');
define('AUTH_SALT', 'uniquestringfive');Try changing define('DOMAIN_CURRENT_SITE', 'community4health.tld'); to this:
define('DOMAIN_CURRENT_SITE', 'www.community4health.tld');
Notice the www in front? You may need it.
Posted 12 months ago #
I just did that and there is no change in the behavior.
I did notice that I do not see the www that we just inserted showing up in address bar.
--------
Too many redirects occurred trying to open “http://community4health.com/wp-login.php?redirect_to=http%3A%2F%2Fcommunity4health.com%2Fwp-admin%2F”. This might occur if you open a page that is redirected to open another page which then is redirected to open the original page.
--------
This topic has been closed to new replies.
