We have about 51 plugins that need to be upgraded. Not sure who should handle this or which release this should be a part of, but we should try to take care of some of the smaller ones (ie., WP-Wiki as opposed to BuddyPress) sooner rather than later . . .
I'll assign this to Boone, but Boone, feel free to delegate. I'd can take this on if need be.
#1 Updated by Boone Gorges over 11 years ago
Don't touch any BuddyPress plugins, as they're generally quite interdependent.
WordPress plugins can and should be updated. It should be easy with Git since there'll be no file restrictions on your local installation. Here's what to do:
- update the plugin via the Dashboard
- git add .
- git commit
- git push
I'd suggest doing four or five per commit, so it doesn't get too tedious.
#4 Updated by Boone Gorges over 11 years ago
I have begun this process. For the moment, skipping BuddyPress plugins and plugins that are otherwise integral to the functioning of the site. (Plugins designed for use on a single blog will generally upgrade without a problem.) With each one, I have activated it and done a very, very perfunctory test, just to make sure that nothing blew up. Below is a list of the plugins ignored on this round:
WordPress MU Sitewide Tags Pages
BuddyPress Group Email Subscription
cets blog defaults
Group Forum Subscription for BuddyPress
I will continue the process sometime soon.
#6 Updated by Boone Gorges over 11 years ago
- Status changed from Assigned to Resolved
I've now upgraded all our plugins, save a few BP-related ones, on all active branches: 1.0-branch, wp-3.0-upgrade, and master. Other plugin upgrades, or problems with any upgrades from this round, should be handled with specific bug or feature tickets.