[wp-trac] [WordPress Trac] #60504: Plugin dependencies: Account for mu-plugin as dependency
WordPress Trac
noreply at wordpress.org
Wed Feb 28 21:38:40 UTC 2024
#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):
[57658] removed the auto-deactivation of plugins with unmet dependencies.
This now means upon updating to WordPress 6.5 an active plugin that has a
dependency that is fulfilled by a mu-plugin will remain active (in the
same way an active plugin with a dependency that is not fulfilled will
remain active).
It remains that an ''inactive'' plugin that has a dependency that is
fulfilled by a mu-plugin will be prevented from being activated, as its
dependency is considered unfulfilled. Bearing in mind that the
introduction of a mu-plugin is a manual process I think this is less of a
pressing concern, but it's my opinion that we do need a way of allowing a
mu-plugin to be recognised as a dependency.
A default mu-loader could be a good idea but we'd need to decide where its
configured list of mu-plugins comes from, it might have to come from
another mu-plugin. I'm not a big fan of filtering the list of
`active_plugins` to lie about what's active as that could come back to
bite, especially if other plugins are reading that option and acting upon
it.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60504#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list