Very lacking documentation

  • DexRuffin

    (@dexruffin)


    4 years, 2 months ago

    The plugin seems to work. There was an issue with custom taxonomies and unfortunately neither the support docs not the support team was able to confirm that custom taxonomies are even supported. They are.

    Documentation is very lacking. Support has replied fast but was sadly not helpful.

    The plugin advertises a free version that supports a variety of feeds. However some of those feeds require data like brand or delivery times which are not WooCommerce standard. To use custom taxonomies or use this plugin to add extra fields such as “Brand” the paid version is required. The free version is not usable for the advertised purpose.

    • This topic was modified 4 years, 2 months ago by DexRuffin.
    • This topic was modified 4 years, 2 months ago by DexRuffin.
Viewing 4 replies - 1 through 4 (of 4 total)
  • supportadtribes

    (@supportadtribes)

    4 years, 2 months ago

    Thanks for your review although not completely accurate.

    When attributes or custom fields are created using the normal WooCommerce interface or using external plugins such as ACF those are supported just fine.

    Thread Starter DexRuffin

    (@dexruffin)

    4 years, 2 months ago

    Problem is that things like delivery times or brands are not product attributes that is why most plugins add these as taxonomies. We do not want the brand or delivery time to appear together with actual product attributes.

    Feel free to let me know if anything changes with the plugin. I am happy to update my review.

    supportadtribes

    (@supportadtribes)

    4 years, 2 months ago

    You can just add them as an attribute (or custom field for that matter) and opt not to show them on your product pages. Like this: https://www.dropbox.com/s/5863s7o5p46df21/JustLikeThis.png?dl=0

    Pretty much all of our users do it like this or use ACF or specific brand plugins with which our plugin is compatible.

    Thread Starter DexRuffin

    (@dexruffin)

    4 years, 2 months ago

    Turns our custom taxonomies are supported by your plugin and the issue was due to a some unrelated conflict. I am not sure why neither the email support nor the replies here were able to confirm and explain custom taxonomies. I moved to a different solution now anyways.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Very lacking documentation’ is closed to new replies.