[wp-trac] Re: [WordPress Trac] #5231: add_action('all', ...) causes unexpected behaviour

[WordPress Trac]

#5231: add_action('all', ...) causes unexpected behaviour
------------------------+---------------------------------------------------
 Reporter:  tellyworth  |        Owner:  anonymous
     Type:  defect      |       Status:  new      
 Priority:  normal      |    Milestone:  2.5      
Component:  General     |      Version:           
 Severity:  normal      |   Resolution:           
 Keywords:              |  
------------------------+---------------------------------------------------
Comment (by tellyworth):

 Fine by me.  I also found three other "all" issues in unit testing:

 1. An "all" filter will mess up the priorities of existing filters when
 merged (already reported in #4715, I can confirm this too)

 2. An "all" action (not filter) causes duplicates: after the "all" action
 has been triggered for action "foo", it exists in two places in
 wp_filters.  Subsequent calls to do_action cause additional duplicates.

 3. Removing an "all" action doesn't work.

 The unit tests will help refactoring, since they cover most of the basic
 behaviour.  They're here: http://svn.automattic.com/wordpress-tests/wp-
 testcase/test_filters.php and
 http://svn.automattic.com/wordpress-tests/wp-testcase/test_actions.php

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5231#comment:5>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software