[wp-trac] [WordPress Trac] #60692: Plugin dependencies: Allow a mu-plugin to fulfil a dependency

WordPress Trac noreply at wordpress.org
Tue Mar 5 12:00:04 UTC 2024


#60692: Plugin dependencies: Allow a mu-plugin to fulfil a dependency
-----------------------------+---------------------
 Reporter:  johnbillion      |       Owner:  (none)
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  6.6
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  2nd-opinion      |     Focuses:
-----------------------------+---------------------
Changes (by costdev):

 * keywords:   => 2nd-opinion


Comment:

 [https://github.com/WordPress/wordpress-develop/pull/6141 The PR] on
 #60504 enables the existing `wp_plugin_dependencies_slug` filter to be
 used to replace Must-Use plugins with their loader file.

 -----

 However, before we consider changing Core to facilitate Must-Use plugins
 as dependencies, I think it would be beneficial to explore the concept of
 standardizing Must-Use plugin loading.

 The benefits for Core and Must-Use plugin users by introducing an easy-to-
 adopt approach to this manual process appear much wider than the Plugin
 Dependencies feature. Additionally, if we made changes to Core to
 facilitate Must-Use plugins as dependencies, then later introduced a
 standardized Must-Use plugin loading layer, then we'd have to maintain
 both.

 There are many implementations of Must-Use plugin loaders out there, which
 is part of the problem in itself. I think we could produce a better result
 if we hold off on coding for now, and begin by exploring the behaviours of
 Must-Use plugin loaders. Essentially a list of **Need** -> **Internal
 configuration layer** -> **Expected outcome(s)**.

 We may even find that rather than a default loader template, this instead
 takes the form of a Must-Use plugin API within Core that Must-Use plugin
 users utilize in their respective loaders.

 Call for opinions: Should we focus on standardizing Must-Use plugin
 loading (via API or default template), and if so, start looking at the
 most basic needs and structure to introduce an early version that's easily
 iterated on?

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


More information about the wp-trac mailing list