WordPress.org

Make WordPress Core

Changes between Initial Version and Version 2 of Ticket #14915


Ignore:
Timestamp:
09/21/2010 01:16:08 AM (10 years ago)
Author:
nacin
Comment:

Corrected, thanks.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14915 – Description

    initial v2  
    33We need to resolve this inconsistency, and either A) fire activation hooks for bulk updates, or B) stop activation hooks from firing for single updates.
    44
    5 I think I suggest (A), despite the backwards compatibility issue. It's unintuitive for an activation hook to be fired on update, and additionally it is not reliable due to manual updates (including SVN). As it is, we silence deactivation hooks on update.
     5I think I suggest (B), despite the backwards compatibility issue. It's unintuitive for an activation hook to be fired on update, and additionally it is not reliable due to manual updates (including SVN). As it is, we silence deactivation hooks on update.
    66
    77Related, a register_upgrade_hook() ticket #14912, that I believe should be wontfix'd. Schema updates require special handling at the plugin level IMO for now.