[wp-trac] [WordPress Trac] #36819: Load plugin.php earlier in wp-settings.php

[WordPress Trac]

#36819: Load plugin.php earlier in wp-settings.php
----------------------------+-----------------------
 Reporter:  jorbin          |       Owner:  jorbin
     Type:  task (blessed)  |      Status:  reopened
 Priority:  normal          |   Milestone:  4.6
Component:  Bootstrap/Load  |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+-----------------------

Comment (by jorbin):

 I don't think reverting is a good idea.

 As `advance-cache.php` is something that isn’t a part of the plugin
 system, there isn’t a good way to update them. I think if you asked most
 users “Are you using an advance cache dropin?” they wouldn’t be able to
 give you a solid answer.  So we have the potential to break sites
 unintentionally.  Is that a change we really want to make after RC2?  What
 is the benefit of reverting?  What do we gain?

 It’s not impossible to remove an already registered filter/action, but it
 is impossible to know about other hooks during the inclusion.  `advance-
 cache.php` could add an action to a later hook and run the removal there.
 Not ideal, but it could be done.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36819#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform