[wp-trac] [WordPress Trac] #20920: Removing all hooks too aggressive if a priority number is given

[WordPress Trac]

#20920: Removing all hooks too aggressive if a priority number is given
--------------------------+-----------------------------
 Reporter:  GeertDD       |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  3.3.2
 Severity:  normal        |   Keywords:  has-patch
--------------------------+-----------------------------
 When you call `remove_all_filters()` or `remove_all_actions()` with a
 priority number (second parameter), all hooks get removed if none is found
 with the given priority.

 Example:

 {{{
 #!php
 <?php
 global $wp_filter;

 add_action('my_action', 'callback_foo');
 add_action('my_action', 'callback_bar', 20);
 var_dump($wp_filter['my_action']);

 // At this point only callback_foo is left. Fine.
 remove_all_actions('my_action', 20);
 var_dump($wp_filter['my_action']);

 // Exactly the same function call as above,
 // but now all hooks bound to my_action are removed!
 remove_all_actions('my_action', 20);
 var_dump($wp_filter['my_action']);
 }}}

 Calling `remove_all_filters()` or `remove_all_actions()` with a priority
 should never remove hooks with another priority.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/20920>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software