Important note: If you are upgrading to WPMu 2.6 and using subdirectories would urge you to check out this post before you commit.
Andy Rush and I sat down yesterday morning and did a “live” screencast of the process for upgrading UMW Blogs from WPMu 1.3.3 to 2.6. It was conceived as a straightforward video for an easy process, but even easy is hard for a moron like me. So forgive all the upgrading bloopers and blunders. This video might be enjoyed more as a cautionary tale of what not to do when upgrading than an informative how-to. It’s availabe for anyone who is considering doing an upgrade but is concened or nervous about the prospect. In fact, the upgrade is quite painless in the end.
Loading ...
But I notice one thing, Jim. In the wp-config file, there’s a new area where it wants long keys–auth-key secure-auth-key and so forth.
That wasn’t there in the previous version, and it asks for long, impossible to guess keys (that you won’t have to remember).
I noticed that you didn’t bother with those. I did, and I’m wondering if it was necessary or not?
And… one more.. Jim- should I upload the wp-content folder?
WordPress is the people’s application! Anyone can play
@Cogdog:
You know I am always up for another domain. In fact, I’ve been itching to map another domain onto my WPMu install. As for the screencast, I can’t believe you watched it given that you are a total rockstar with all things WPMu. Your most recent WPMu post taught me about ten trick for hacking the site, you really have too much free time. Nonetheless, I do love that you heard me ignore your advice in the screencast. I’m an uppity son of a bitch
But I saw that you did some mistakes along the way
I saw that you have a plugin to let users edit their theme. Aren’t you worried about people who can put php code or javascript code in the theme?
@Joe
Those strings are used by wordpress to encrypt the passwords with the “salt” technique. Basically what it does is take your password, merge it with the encryption key and only then it encrypts it with md5. The old wordpress would of just encrypted the password alone.
Until now, the md5 string of a password would of been the same on your blog as anywhere else. Meaning that a hacker that would of got their hands on a md5 string could of brute forced that password.
Now, with the encryption keys, your password can’t be hacked because it can’t be brute forced. They would need the encryption keys.
Many, many mistakes
As for Userthemes, this is something we allow on a case-by-case basis, we know who is using it, and it gives us all the theme customization options of a single WP install, which is very nice. And, to be clear, not everyone who has a blog on UWM Blogs can edit their themes, that is something we give them permissions to do, and help them with along the way.
Also, thanks for the clarification on the salt technique, it was quite useful.
I also did some translations and a custom spam filter, so its a bit harder for me to upgrade.
But I will do it eventually.
Also, I have a lot of themes on my site and none of them support tags, so I would have to edit each one and add the tags function.
And since I have over 2300 blogs, I will edit he page that ugrades the blogs and set it to update 50 blogs at a time not 5 like it is default. That way I don’t have to wait half an hour or more.