Proof Health
Open evidenceCommercial opportunities need traceable source links before they are treated as build-worthy.
100.0% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Related Opportunities
0 marketsNo opportunity report currently maps to this plugin's tags.
Source Evidence
Open evidence explorerHow-to Guide?: users show security, compatibility, support pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Dependency issues on a network installation: users show bugs, compatibility, migration pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] conflict management idea for "Provides": users show compatibility, missing feature, support pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Plugin Dependencies: users show bugs, compatibility, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Can it be configured based on theme?: users show compatibility, missing feature, setup pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Possible to automatically download and activate dependent plugins?: users show missing feature, support, setup pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] Suggestion: users show compatibility, setup pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] Unreliable plugin naming/identifying scheme: users show bugs, compatibility, setup pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Disable rather than deactivate?: users show missing feature, support pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] Dependent plugins can still be activated with "Bulk Actions": users show bugs, missing feature pain that may indicate a product gap.
This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Competitor Context
1 shownRepeated Themes
0 shownNo repeated plugin-level themes have been generated yet.
Collected Signals
20 shown from 22 collectedWhis Is Sadly Missing From WP Core: users show missing feature pain that may indicate a product gap.
Evidence: Whis Is Sadly Missing From WP Core This plugin — with its companion Known Plugin Dependencies — offers basic, and that is to say: robust — plugin dependency information and handling.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
I think this should be in Core: users praise value, which suggests what competitors already do well.
Evidence: I think this should be in Core I have been asking WordPress to add some sort of plugin dependency for quite some time now.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Excellent: users praise quality, which suggests what competitors already do well.
Evidence: Excellent This plugin should be WordPress core functionality.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
This should be in core: praise conversation with limited structured signal.
Evidence: This should be in core Should be WordPress core functionality. Should be WordPress core functionality.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Good Work: users praise reliable, which suggests what competitors already do well.
Evidence: This is what I came to find how it works in wordpress I completely agree (about that it should be in core of course) !This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Possible to automatically download and activate dependent plugins?: users show missing feature, support, setup pain that may indicate a product gap.
Evidence: Possible to automatically download and activate dependent plugins?This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Version number is incorrect in 1.3 file header: users show bugs, compatibility pain that may indicate a product gap.
Evidence: Version number is incorrect in 1.3 file header Hi, great plugin.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Good work: praise conversation with limited structured signal.
Evidence: Good work Useful, thanks Useful, thanksThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Awsome: praise conversation with limited structured signal.
Evidence: Awsome Wow… just that I’m looking for. Wow… just that I’m looking for.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Satisfied vs. Network Unsatisfied: users show support pain that may indicate a product gap.
Evidence: But it would also help to understand conceptually what “unsatisfied network” means.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
mu-plugin support added: users show missing feature, support pain that may indicate a product gap.
Evidence: mu-plugin support added I added code to the plugin to show dependencies on MU plugins.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Can it be configured based on theme?: users show compatibility, missing feature, setup pain that may indicate a product gap.
Evidence: Can it be configured based on theme?This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Dependency issues on a network installation: users show bugs, compatibility, migration pain that may indicate a product gap.
Evidence: Dependency issues on a network installation I have a network WordPress setup where Plugin Dependencies is activated network-wide.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
How-to Guide?: users show security, compatibility, support pain that may indicate a product gap.
Evidence: Up-front, I’m a php newbie, so sorry if this seems dumb.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Disable rather than deactivate?: users show missing feature, support pain that may indicate a product gap.
Evidence: Keeping it with an activated status will help when upgrading plugins and when deactivating plugins by accident and not realising other plugins have been permanently deactivated.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
Brilliant :-): praise conversation with limited structured signal.
Evidence: Brilliant :-) This needs to be a core function of WP. It is especially useful when developing large projects, and the custom code is split into a handful of plugins to handle distinct functionality. Being able to handle dependencies like this avoids many white screens and scratching of heads. This needs to be a core function of WP. It is especially useful whThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] Dependent plugins can still be activated with "Bulk Actions": users show bugs, missing feature pain that may indicate a product gap.
Evidence: I found a bug though.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] Unreliable plugin naming/identifying scheme: users show bugs, compatibility, setup pain that may indicate a product gap.
Evidence: [Plugin: Plugin Dependencies] Unreliable plugin naming/identifying scheme I can’t figure out what the standards or requirements are for plugin naming in wordpress.This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] conflict management idea for "Provides": users show compatibility, missing feature, support pain that may indicate a product gap.
Evidence: [Plugin: Plugin Dependencies] conflict management idea for "Provides" Instead of disabling the conflicting plugins outright, can some variable or option be set, notifying the plugins of the conflict?This row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.
[Plugin: Plugin Dependencies] You can deactivate plugins even if dependencies are not deactivated: neutral conversation with limited structured signal.
Evidence: [Plugin: Plugin Dependencies] You can deactivate plugins even if dependencies are not deactivated When I deactivated a plugin which had a dependency I was allowed to do that and I was unable to re-active the plugin. The Active button was replaced with the Edit button (as in edit plugin in editor). http://wordpress.org/extend/plugins/plugin-dependencies/ WhenThis row is useful source evidence, but it has not been promoted into a build-worthy commercial opportunity.