Support » Plugin: WooCommerce No Shipping Message » Please declare required and supported WooCommerce version in main plugin file

  • Hi Dan,

    Thanks for great plugin!

    Would you consider declaring required and supported WooCommerce version in main plugin file? See: https://docs.woocommerce.com/document/create-a-plugin/#section-10

    For example: WC requires at least: 4.0 and WC tested up to: 4.1.

    Now there’s an ugly warning on Plugins page in backend that there is no compatibility information for this plugin available whenever new version of WooCommerce is out. It’s a pity, since your plugin works just fine with recent WooCommerce version.

    Cheers,
    Česlav

Viewing 3 replies - 1 through 3 (of 3 total)
  • I just noticed you have these headers in readme.txt file. It seems that WooCommerce can only pick them up from main plugin file. I guess it’s because readme.txt is only required for plugins published in WordPress.org Plugins Directory.

    Requires at least, Tested up to and Requires PHP headers can be put in main plugin file as well, see: https://developer.wordpress.org/plugins/plugin-basics/header-requirements/ Although I have no idea whether main plugin file or readme.txt is preferred by Plugins Directory.

    Plugin Author Dan

    (@dangoodman)

    Thank you for the report. Just added the ‘WC requires at least’ and ‘WC tested up to’ fields to the main plugin file.

    However, the issue is that WooCommerce looks for those fields in the locally installed plugin files. Unlike WordPress, which fetches the compatibility information from the wp.org API. That means WooCommerce will always show that ugly message until you update the plugin.

    Thanks for quick response!

    I know that plugin’s compatibility version is only checked locally, but it still helps to see what it is. If I’m going to upgrade WC to 4.1 and some WC extension is compatible up to 4.0, my concerns are not as big as they would be in case of 3.x.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.