[wp-trac] [WordPress Trac] #20995: [20525] breaks commonly used plugin technique for network activation

[WordPress Trac]

#20995: [20525] breaks commonly used plugin technique for network activation
-------------------------------+--------------------
 Reporter:  iandunn            |       Owner:
     Type:  defect (bug)       |      Status:  new
 Priority:  normal             |   Milestone:  3.4.1
Component:  Multisite          |     Version:  3.4
 Severity:  normal             |  Resolution:
 Keywords:  close 2nd-opinion  |
-------------------------------+--------------------

Comment (by WPReady):

 We want to point out some observations about this discussion:

 Reading http://wpdevel.wordpress.com/2010/10/27/plugin-activation-hooks-
 no-longer-fire-for-updates/  we interpreted no hook is reliable to detect
 updates.

 We almost thought that activation hook was an ideal place to detect
 updates. We were wrong.

 So, we followed the recommendation about the right way to do it. The
 current strategy rests over another hook(plugins_loaded) which supposedly
 it fires when the plugins are loaded, and also an option value to check if
 there were changes. This concept worked fine.

 From the moment we knew updates couldn't trigger activation we also
 assumed there is no deactivation trigger .  It is like the plugin passed
 through the updating process
 without triggering hooks.

 Trying to reuse the actual solution, we ended up parsing the url referrer
 to decide what to do.  In this scenario $network_wide variable isn't
 useful, because we discarded the hooks.

 What it would be the current recommendation? Thanks.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/20995#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software