[wp-trac] [WordPress Trac] #37646: Make wp-settings.php a series of do_actions()

[WordPress Trac]

#37646: Make wp-settings.php a series of do_actions()
--------------------------------------+------------------------------
 Reporter:  johnjamesjacoby           |       Owner:
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:  Awaiting Review
Component:  Bootstrap/Load            |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  2nd-opinion dev-feedback  |     Focuses:
--------------------------------------+------------------------------

Comment (by MikeSchinkel):

 Replying to [comment:5 jorbin]:
 > My biggest worry with tying all includes to actions is that it would
 make all of WordPress pluggable and that feels like a great way to
 increase breakage on updates.

 I definitely can see @jorbin's perspective.  Making WordPress easier to
 break has the potential for rogue plugin author to break sites for  users
 unable to fix the problem or even understand the problem, and that makes
 WordPress look bad, in users eyes and in the eyes of a press who likes to
 sensationalize problems.

 Replying to [comment:6 DrewAPicture]:
 > There's an immense upside in enabling proverbial forks of WordPress to
 do what they wish with how WordPress is loaded

 And yet I definitely see @DrewAPicture's perspective, because I am usually
 in this position of wanting to get WordPress to work they way I need it to
 work for a highly customized site yet I am stymied because of some
 limitation baked into core. For those of us building custom sites for
 businesses, this lack of flexibility turns out to be a huge downside and
 perpetuates the ''"WordPress is just a blog"'' mentality among IT
 professionals and those business people who parrot them.

 What's the middle ground?

 I've often thought that there should be something that a plugin can't to
 and a theme can't do but that a custom site builder could do to turn on
 ''"unsafe"'' features, such as having a constant defined in `wp-
 config.php` that, once defined, allows custom site builders to shoot
 themselves in the foot, if we so desire. But themes and plugins could not
 do it unless they get the their end-users to manually update `wp-
 config.php`, which most won't want to do because of the bad user
 experience required.   OTOH I've never before proposed it because I always
 feared that too many people would see it as not ''"the WordPress way."''
 FWIW.

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