[wp-trac] [WordPress Trac] #48050: Development Build: Provide structure to auto-install plugins

WordPress Trac noreply at wordpress.org
Tue Sep 17 15:34:53 UTC 2019


#48050: Development Build: Provide structure to auto-install plugins
------------------------------------+------------------------------
 Reporter:  kraftbj                 |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Build/Test Tools        |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+------------------------------
Changes (by kraftbj):

 * keywords:  has-patch => has-patch dev-feedback


Comment:

 I can appreciate that. There are two issues:

 1. Adding the framework to be able to auto-install plugins based on
 environmental variables. I think there's no objection to having that in
 place so far in this ticket.

 2. The perhaps questionable bit: Whether or not Core should auto-install
 any particular debugging plugin as part of the local development package
 out of the box.

 I'm okay and would push to be just a little opinionated in terms of Query
 Monitor. In a perfect world, I'd love if Debug Bar was the quintessential
 debug plugin (as it is developed by the "WordPress.org Team"), but it
 isn't. In virtually all circles, Query Monitor _is_ that plugin. There are
 definitely other debug plugins to install also (to the point of the
 comment in #42879), but no matter what you're doing in WP, Query Monitor
 covers things relevant. I think being opinionated to the point of strongly
 encouraging developers (for Core or plugins/themes as they begin to use
 this local dev environment) to keep tabs on what QM outputs is an overall
 good thing——plenty of plugins are submitted to the repo with obvious
 issues, like PHP warnings, that were missed before submission.

 That said, if the concept of environmental variable leading to plugin
 install is only blocked by whether or not Query Monitor should be
 installed, I'm perfectly fine with a compromise of infrastructure only. It
 can always be added later if the demand/need is present.

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


More information about the wp-trac mailing list