Then for most if not all ".# " updates, deactivating plugins should not
be neccessary at all. However, for major milestones it's probably a very
good idea to deactivate all active plugins beforehand. Then again, it's
probably a very good idea not to use the core auto-upgrade feature at
all when upgrading to the next major milestone anyway.
On 12/7/2008 12:37 AM, Ryan Boren wrote:
On Sat, Dec 6, 2008 at 6:41 AM, Kirk M<[EMAIL PROTECTED]> wrote:
I know this was asked before but I've forgotten. In the past I've always
deactivated all my plugins manually before updating the core. Now I find
myself using 2.7's auto-update feature the same way--the second thing I do
before updating is to bulk deactivate all my plugins (first is to backup
DB). So...
Does running 2.7's new core auto update automatically deactivate plugins
before updating and reactivate them after it's finished or does that still
have to be done manually?
During the upgrade, your blog is put in maintenance mode and loading
is halted at the beginning of wp-settings.php. Nothing really runs,
including plugins. The only thing allowed to run is the DB upgrade,
which takes care of making sure plugins are not loaded. You don't
need to deactivate plugins unless you like turning them back on
one-by-one after upgrading to isolate any breakage they might cause.
_______________________________________________
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
wp-testers@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers
