• I really wanted to like this plugin and when I started using it, on the face of it, everything seemed promising and good. However, it turned out to be very unstable.

    First, I’ve noticed that after its installation the custom fields in the product pages displayed in their dropdown field only attributes related to this plugin and stopped displaying all the other attributes. I’ve reported that but the issue hasn’t been resolved. I eventually resolved it myself with a custom function and moved on. At that point, everything was working fine.

    Then, after I had updated the plugin to v13.4.9 and tried to manually refresh a feed, it didn’t respond and didn’t update the feed (while the option ‘Disable HTTP feed generation requests’ had its ‘off’ default). Also, the feeds dropdown fields of attributes and values didn’t auto-fill like they used to. I’ve noticed in devtools the js errors select2 is not a function and tipTIP is not a function.
    I’ve examined the issue extensively, and came to the conclusion that the new plugin update doesn’t support all the (relatively recent) older version of WP and WC like the ones I use: WP 6.6.4 with WC 9.3.3 – which I personally can’t update due to heavy customization.

    To summarize the issue briefly, after the update, the plugin now depends on newer Select2/TipTip registration method which is not supported in WP 6.6.4 / WC 9.3.3 and therefore the injection of adt_nonce fails which, in turn, breaks the script and certain functionalities.
    I then replicated the same issue also on another website, with all plugins disabled except Woocommerce and this plugin, and with WP default theme.

    I’ve submitted a support ticket with a more detailed analysis, and the developers may or may not resolve this at some point.
    However, it’s irrelevant for me if they resolve it or not, as I came to the conclusion that it doesn’t matter, as this plugin doesn’t seem reliable and stable. There’s no point in being anxious with every single one of its future updates of what would now break… I think its code is poorly executed, not being tested extensively for backward compatibility, and when that’s the case, other things WILL break.
    Besides that, the plugin doesn’t output UTF-8 encoding in the feed declaration or provide encoding options and doesn’t have the option to modify the order of feed attributes.
    Considering everything, I’ve decided to move on to a different plugin which seems more stable and better coded.

The topic ‘Unstable and poorly coded’ is closed to new replies.