Forum Replies Created
-
You’ll have to move from wordpress to wpmu first.
http://mu.wordpress.org
I’m just finishing up a post on how to do backups.“I thought about the index.html as well, but that would still make people loose their posts they are editing when upgrade is taken place (or is failing), wouldn’t it?”
Hopefully you’ll have booted them out & warned them.
Don’t upgrade on the middle of a Thursday, for instance. First thing Monday morning, early on a Saturday – those are times I pick, though I also have the advantage of being in an earlier timezone than my users.“So you also do not (even) deactivate the BP-plugins?”
I mostly do MU sites, but yeah. I’d just keep on going… (Do the instructions say to deactivate it? I can’t say I ever looked…)
I tyr the auto-upgrades first, and then if needed (or if it’s a big upgrade) I do it manually. Much safer.
“By the way, myself and some others had a white screen of death last upgrade. Not just just main blog, but all blogs, the moment I clicked the de-activate BuddyPress button. Apparently this could have been prevented by switching theme first”
Yep. the theme is looking for BP and you turned it off.
Kind of predictable, really.I did a post here about backups, mostly via ssh, if someone wants to give it a read-over.
Plan for the upgrade and pick a time when your site traffic is low.
Let your users know ahead of time that you’ll be down for maintenance. Even with just a few users, letting them know is a courtesy, because if they do visit while you’re upgrading and they don’t know what’s going on, they may eventually leave because they think things break all the time.
Yes, we backup ahead of time. Really. With large site where it would be impossible to ftp things without it taking all day, just backup files in a different location on the server. Optimize & clean up the db while you’re at it. Who wants to back up spam?
Some of us with large sites do not deactivate all plugins and then reactivate later. With hundreds or thousands of blogs, it’d be a nightmare.
At some point when your site is very large, you’re just going to have to get used to doing some things command line (ssh). In many ways, it’s easier.
The moving of the them only occurred during BP 1.1. Shouldn’t have to do it next time. But! Paying attention to core changes helps you anticipate these things in advance. You have to do your homework.
The maintenance mode plugin may not work properly in MU. My fave trick, if I*really* wanna keep people out, is to toss an index.html file in the root. I can still get in the backend, but many users just can’t figure out they can type in these things without a link there.
Man, this means I have to write up a blog post about it now, doesn’t it?
“We have spent around three months with the wordpress and bp software. “
I’ve spent three years working with WordPressMU (before it was in beta even) and the job you’re talking about is *huge*. Like others have said.
Tip: start in phases. Pick something basic you can start with then build off that. Even the example given about with the tuts plus network, they started with one blog.
you also have to offer value, and in being different, phrases like “like youtube” don’t help.
Yep.
Single WP could have multiple users all along. To answer the OP, if you want to start building on WPMU now, go right ahead. You won’t need to re-do anything after the merge. The hope is the upgrade will be quite smooth. You’ll just be upgrading to the “regualr” WP codebase, but your multiple blogs are alreayd turned on in wp-config.
If anything, it’s single WP going away.
@nocomment yeah, we’ve fiddled and tested BP & multisite together.
@DJPaul – will investigate right-quick!
There are cases where clients have a use for multiple sites, each with its own distinct buddypress. So that would be cool. (I think we’re working on a trac ticket – don’t hold me to it yet tho)
Edit: quick confer with Ron, and the multi-blog part is a seperate isue than on multiple sites.
Still thinking.
That’s a mod_rewrite issue. Either it’s not installed on your server, or the htaccess file isn’t being read.
just tell your webhost support that your WP permalinks aren’t working. They should know what to do then.
