I would imagine you’d be best to take the plugins out of mu-plugins and put them in a new folder called “temp”, upgrade BP, and then replace the files back into mu-plugins.
The reason why this is necessary (for now) is because plugins that depend on BuddyPress being active do not have a dedicated way to check for its existence, and will die when BP isn’t there.
This will be addressed in future versions.
The only plugins that need to be deactivated are those that are dependent upon BuddyPress. So, if you don’t have any of those in mu-plugins, you should be fine keeping them as is.
Andy is working on some code that will automatically deactivate all BP-dependent plugins whenever BP gets deactivated. Of course, this code will need to be retroactively added to all current BP plugins out there, but I imagine plugin devs will simply add this coding to one of their next versions.
That makes things clearer. So this is what I plan to do.
Backup the whole WPMU install directory(or is wp-contents enough?)
Backup the database
Deactivate all BP related plugins in the plugins folder
Move out BP related plugins from the mu-plugins folder
Deactivate BP
Click the upgrade thingy for BP
Activate BP
Move/Activate the rest of the plugins
I’ll be doing this over the weekend. Hopefully all goes well as I am running it on a live site.
Thanks for your help guys.
Another newbie question..does deactivating plugins reset their settings? (I am guessing not)
I just updated using the above steps and there aren’t any immediate errors so I am happy about that. I will do some more testing to make sure everything is working fine.
Another question: Are there any upgrades to the default member & home themes from 1.0 to 1.0.2? I have (slightly) modified versions of both and I was wondering whether I need to overwrite my themes from the 1.0.2 versions as well.
@Kunal17
Another question: Are there any upgrades to the default member & home themes from 1.0 to 1.0.2?
Yes. There have been an number of changes and improvements. You have two choices:
- Make a copy of the v1.0.2 default themes and modify those copies to match your current theme customizations
- Or, go through the changesets in trac starting here and look for any theme changes and then make those in your current themes
Jeff,
Thanks for the advice. Looking at https://trac.buddypress.org/browser/trunk/bp-themes?rev=1468, I see a few changes in both the member as well as the home theme to make them compatible with Firefox 3.5. The other changes are 2 months old (which would make them older than BP1.0 that I was running before I updated)
Sorry to trouble you, but can you confirm that this is all that has changed in 1.0.2. I believe that even in the listed changes on the blog post, this is the only change that could correspond to the default themes. Ive tried to dig further, but I am not very familiar with the trac system.
Kunal17-
What I meant was you start at that changeset (r1468) and go through all of the changesets up to the current one (r1593). Although, you should be okay only going up to r1577. So, that is at least 109 changesets you have to search through. To navigate through the changesets, look near the upper right-hand cornor. You’ll see these links:
<-Â Previous Change | Next Change ->
Look for any changes to the theme files. I do not know how many of the revisions deal with themes.
Thanks Jeff,
I was able to make the necessary changes.
@Kunal17,
Were there a lot of changes to the member themes?
I’m planning on upgrading to BP 1.0.2 myself and I have a somewhat, customized member theme.
ray, I have been keeping track of which core & theme files I modify.
I went through the various changesets like Jeff described above to see whether any of those files were changed and just made those changes on my old versions of those files and copied over the rest from the new versions.
Overall I had to edit less than 10 lines over 4-5 of my modified files to update my themes to BP1.0.2
I was really looking for changes made to bpskeletonmember theme, so I only made two changes to two files (if I remember correctly!)
