[wp-trac] [WordPress Trac] #60504: Plugin dependencies: Account for mu-plugin as dependency

[WordPress Trac]

#60504: Plugin dependencies: Account for mu-plugin as dependency
-------------------------------------------------+-------------------------
 Reporter:  johnbillion                          |       Owner:  costdev
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.5
Component:  Upgrade/Install                      |     Version:  trunk
 Severity:  critical                             |  Resolution:
 Keywords:  needs-testing dev-feedback has-      |     Focuses:
  patch has-unit-tests                           |
-------------------------------------------------+-------------------------

Comment (by johnbillion):

 [https://github.com/humanmade/mu-plugins-loader At Human Made we have a
 package for doing the same thing], except it supports defining the list of
 mu-plugins either via a PHP constant or via a config entry in
 `composer.json` for Composer based projects. Essentially the same thing,
 minus filtering the `active_plugins` value, which I don't yet have an
 opinion about.

 A default mu-plugin loader could be a good idea. Would it need to consider
 handling conditional logic that is present in, for example,
 [https://github.com/Automattic/vip-go-mu-plugins/ the WordPress VIP mu-
 plugins]? Conditionally defining the array of mu-plugins to load would
 mean centralising a lot of the logic that is currently separated into
 multiple mu-plugin loaders.

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