Parses a 'Requires Plugins' header. If a requiring plugin does not have all its dependencies installed and active, it will not activate.

Andy Fragen

Colin Stewart

Paul Biron

Parses a ‘Requires Plugins’ header. If a requiring plugin does not have all its dependencies installed and active, it will not activate.
<a href="https://make.wordpress.org/core/2022/02/24/feature-project-plugin-dependencies/" rel="nofollow ugc">Make post for Plugin Dependencies Feature Project</a>
Please open issues at <a href="https://github.com/WordPress/wp-plugin-dependencies/issues" rel="nofollow ugc">WordPress/wp-plugin-dependencies issues</a>
My solution to <a href="https://core.trac.wordpress.org/ticket/22316" rel="nofollow ugc">#22316</a>. Feature plugin version of <a href="https://github.com/WordPress/wordpress-develop/pull/3032" rel="nofollow ugc">PR #3032</a>
<ul>
<li>Parses the Requires Plugins header that defines plugin dependencies using a comma separated list of wp.org slugs. To test, you will need to add the header and content to a plugin.</li>
<li>In the plugins page, a dependent plugin is unable to be deleted or deactivated if the requiring plugin is active.</li>
<li>Plugin dependencies can be deactivated or deleted if the requiring plugin is not active.</li>
<li>Messaging in the plugin row description is inserted; as is data noting which plugins require the dependency.</li>
<li>Ensures that plugins with unmet dependencies cannot be activated.</li>
<li>Circular dependencies cannot be activated and an admin notice noting the circular dependencies is displayed.</li>
<li>Ensures that plugins with unmet dependencies cannot be activated.</li>
</ul>
There are several single file plugins that may be used for testing in <code>test-plugins/</code>.
<h3>Pull Requests</h3>
PRs should be made against the <code>develop</code> branch.

Plugin Dependencies

There is a good plugin, but the plugin page is very crowded and getting to the bottom of the page happens later, which is not good for everyone.
An option must be added so that the user or developer can easily enable or disable the display of this plugin information from the page settings at the top of the plugins page.

GOOD and BAD

Would be cool to see this in themes as well

Alternatives to Plugin Dependencies

Top alternatives