[wp-trac] [WordPress Trac] #4715: Possible Lost of Priority with Merge_filters and $wp_filters['all']

[WordPress Trac]

#4715: Possible Lost of Priority with Merge_filters and $wp_filters['all']
------------------------+---------------------------------------------------
 Reporter:  darkdragon  |       Owner:  anonymous                             
     Type:  defect      |      Status:  new                                   
 Priority:  normal      |   Milestone:                                        
Component:  General     |     Version:  2.3                                   
 Severity:  normal      |    Keywords:  has-patch merge_filters filters plugin
------------------------+---------------------------------------------------
 I have asked why the merge_filters has array_merge for both
 {{{$wp_filters['all']}}} and {{{$wp_filters[$tag]}}}, when this will lose
 the priority information. I suppose this doesn't come up since not many
 plug-ins setup {{{$wp_filters['all']}}}.

 I expect the desired result to be appended '''with''' priority information
 intact.

 http://wordpress.org/support/topic/129404?replies=1 has more information.

 {{{
 if ( isset($wp_filter['all']) && is_array($wp_filter['all']) )
     $wp_filter[$tag] = $wp_filter['all'] + (array) $wp_filter[$tag];
 }}}

 Is the desired result the lost of priority information when
 {{{$wp_filter['all']}}} is used?

 Question: I'm not going to set the milestone. Am I supposed to set that?
 Some trac sites don't like that.

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