• Hi,

    The latest Woo Commerce update reports that this plugin is not known to be compatible with Woo Commerce version 3.0 (or later).

    WooCommerce just release its new version check so for every plugin that doesn’t have special tags in its header, it reports unknown compatibility.

    Can you please supply information to Woo Commerce so it will know whether or not this plugin is compatible?

    If you have any other woocommerce plugins, then they may need checking too.

    Thanks

    [note – sent 5 minutes after “same message” to another plugin, which also has the same problem]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Andrew Gunn

    (@amg26)

    This plugin is honestly a mess. I tried to reverse engineer a similar plugin and this really never materialized into something stable enough for me to be able to manage. How it is now is about as far as I can take it without doing a complete rebuild.

    I apologize but this is just the honest truth. I would say to use at your own risk, I have no idea about compaitibliy with Woo versions or theme versions.

    The nightmare with this type of Woo plugin is theme compatibility. It is dependant on certain classes and HTML structure to exist otherwise it won’t work. Its targeted for the basic Store core theme built by WooCommerce. Trying to cover every different variation is just impossible and too time consuming to work on.

    Thread Starter MKSnMKS

    (@mksnmks)

    Hi Andrew,

    2) Sub-Topic – “mess
    2-pii) “apologies”
    Wow – great words!
    Please continue to be (relatively) fearless.
    It is better to apologize for honest truths, than to not apologize for other truths, though its good to apologize for all types of truths.
    2-pi) “mess”
    General approach to “mess”es

      try to compartmentalize.
      break the situation down to smaller manageable situations.
      avoid compounding and mixing up.
      see which sub-messes are least problematic (or even are okay).
      address the sub-messes which are most critical.
      put things back together and test.
      repeat to refine.

    2-piii) I can only image the difficulties with compatibilities with themes (and possibly other plugins). It might be possible to collect information from users who have tested it with their theme, to build a list of themes that it works well/okay/partially with and those that it does not.
    This becomes very easy to collect if the user can just click a button to send the details direct to database list, rather than compose emails that need custom handling.

    Some thoughts;
    a) the decision process could be treated like a module, that is known to handle certain situations, so the main plugin is installed, the user theme is detected (or list of themes entered), then the plugin installs the decision module.
    b) a generic module could be used to test theme of unknown compatibility, and problems can be reported back to a database (similar to above). So eventually somebody (other team member?) can compose a module that works.
    c) theme creators might be interested in writing a module specifically for their own theme(s).
    d) consider page builders that can work with very minimal themes, as a recommendable environment for this plugin.

    1) Main Topic – unknown compatibility with WooCommerce (latest versions)
    The plugin can work well or only in some circumstances, with WooCommerce.
    But that is not the problem.
    The problem is that it is not “declaring” that it works with WooCommerce, by using the header tags that the latest versions of WC require.

    There have been quite number of other plugins that have had the same problem, and fortunately KaggDesign was kind enough to let me know what the fix is so I can let the other plugins know.
    See Below.

    Thanks for getting back to me on this.
    A bit slow, but better late than never.
    I hope things have been alright, and that this fixes the problem.
    Keep up the good work.

    Please can you let me know if this helps?

    Thanks

    ========================================

    The fix for this is provided below, by
    kaggdesign author of WOOF by Category,
    which had alerted to the same problem,
    and they found the fix.
    So thanks Kaggdesign

    Hi,

    It is very simple. Open main plugin file /wp-content/plugins/woof-by-category/woof-by-category.php and in the first lines you can see the plugin header

    /**
    * Plugin Name: WOOF by Category
    * Plugin URI: https://www.ads-software.com/plugins/woof-by-category/
    * Description: WooCommerce Product Filter (WOOF) extension to display set of filters depending on current product category page.
    * Author: KAGG Design
    * Version: 1.5
    * Author URI: https://kagg.eu/en/
    * Requires at least: 4.4
    * Tested up to: 5.0
    * WC requires at least: 3.0
    * WC tested up to: 3.3
    *
    * Text Domain: woof-by-category
    * Domain Path: /languages/
    *
    * @package WOOF by Category
    * @author KAGG Design
    */

    Lines (bold-ed above)

    * WC requires at least: 3.0
    * WC tested up to: 3.3

    are responsible to reflect compatibility with WooCommerce.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘latest WooCommerce unknown compatibility – WooCommerce Custom Overlays’ is closed to new replies.