[wp-trac] [WordPress Trac] #8833: extract pluggable.php function logic into separate functions

[WordPress Trac]

#8833: extract pluggable.php function logic into separate functions
--------------------------------------------+-----------------------------
 Reporter:  wnorris                         |       Owner:  Viper007Bond
     Type:  enhancement                     |      Status:  new
 Priority:  normal                          |   Milestone:  Future Release
Component:  Plugins                         |     Version:  2.8
 Severity:  normal                          |  Resolution:
 Keywords:  needs-patch dev-feedback close  |
--------------------------------------------+-----------------------------
Changes (by bpetty):

 * cc: bpetty (added)
 * keywords:  needs-patch dev-feedback => needs-patch dev-feedback close


Comment:

 I believe this ticket is just sitting here with no action because when it
 comes down to it, it doesn't actually solve anything, or make it any
 easier to implement multiple related plugins to work together. In fact, it
 would actually make it even harder to predict what is going to happen when
 a pluggable method is called.

 As @azaozz pointed out, only one plugin overriding a pluggable method
 wins, period. It doesn't matter if it's still possible to call the default
 method or not, the fact remains that it's no longer being called reliably
 100% of the time, and letting another plugin still call the default
 implementation would then mean that the original plugin overriding the
 pluggable method then technically breaks since it's not reliably being
 called when it should be either. The proposed patch doesn't fix the "one
 plugin wins" scenario, it just makes it more complicated.

 When it comes down to it, @johnbillion is right. This really just comes
 down to individual use cases where additional actions and filters may be
 necessary to still encourage core usage rather than implementing pluggable
 methods (which is definitely still preferred), and if a plugin does
 implement a pluggable method, nothing in core is going to be able to do
 anything about it. It's the responsibility of each plugin to ensure
 compatibility with the other plugins that do it (which is still perfectly
 possible without any changes in core code or behavior currently).

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