Proposal: Add 'CF7 tested up to' readme header support

[maxguru]

This isn't really a bug but a feature request.

WooCommerce supports the 'WC tested up to' readme header for plugins that integrate with the plugin. I propose a similar 'CF7 tested up to' readme header support (for plugins that integrate with Contact Form 7). Additionally, users that attempt to upgrade Contact Form 7 can be warned about possible issues due to lack of support in other plugins, similarly to how it is done with WooCommerce.

Any thoughts?

[maxguru]

The header 'CF7 requires at least' would also be helpful.

[takayukister]

Sounds interesting. I think the header naming needs more polishing, though.

[maxguru]

To be honest, I think WordPress itself needs to have this feature.

[takayukister]

Yeah, I think so, too.

There is no way for a plugin to know whether its add-on plugins are used.

[maxguru]

If they are active then they might be used. My thinking was, it would have been nice for WordPress core to have functionality for resolving plugin dependencies. Something similar to composer. Maybe they can switch to that someday. Meanwhile, it would be nice to have some solution that would alert the user about a possible problem prior to updates.

[pwkip]

Just one possible approach. What do you think about adding a global variable $wpcf7_third_party_extensions?

This could hold an array of arrays/objects that look something like this:

[
  'contact-form-cfdb7' => [
    'tested_up_to' => '5.4',
    'requires_at_least' => '3.0'
  ],
  'wpcf7-recaptcha' => [
    'tested_up_to' => '5.4.1',
    'requires_at_least' => '5.0'
  ],
]

Then, if you make it filterable,

$wpcf7_third_party_extensions = apply_filters( 'wpcf7_third_party_extensions', [] );

third party plugins would be able to declare WPCF7 support like this:

add_filter('wpcf7_third_party_extensions', function($wpcf7_third_party_extensions) {
    $wpcf7_third_party_extensions['cf7-conditional-fields'] = [
        'tested_up_to' => '5.4.1',
        'requires_at_least' => '5.4'
    ];

    return $wpcf7_third_party_extensions;
});

You could then show upgrade notices based on the information present in this variable. Additionally, there could be a dismissible admin notice if you detect conflicting plugins.

Some potential problems:

• It will only work for plugins that are activated.
• It will only work for plugins that have explicitly declared support in this way. (But that's the same for WooCommerce)

[Zodiac1978]

To be honest, I think WordPress itself needs to have this feature.

There was a time this was an active idea ... resulting in this plugins:
https://de.wordpress.org/plugins/plugin-dependencies/
https://de.wordpress.org/plugins/known-plugin-dependencies/

Starting point was: https://core.trac.wordpress.org/ticket/22316

Additional ideas:
https://core.trac.wordpress.org/ticket/40460
https://core.trac.wordpress.org/ticket/43882

[Zodiac1978]

The latest solution is this feature plugin: https://wordpress.org/plugins/wp-plugin-dependencies/
(From: https://make.wordpress.org/core/features/)

Although, it only prevents activating the plugin if the dependencies are not met, and it prevents deactivating or deleted if the plugin is required by another plugin.

This line ("Requires Plugins") need to be added in the add-on plugin.