Is it safe to use performance wise

  • The woocommerce team has taken serious misstep back in 2018. I have been using the woocommerce since 2017 but all my product attributes are of type multiselect. So I didn’t observed the change. I understand the woocommerce team concern but their fix to add a new field is not actually a fix, but a pain. It is prone to create a lot of inconsistent data due to mispell, because I couldn’t enforce the attributes name now.

    Now I want to create another book store which should have isbn13, isbn10, pages, bookauthor, publisher, pages and language attributes of type text.

    Would this plugin be suitable for large number of products?

    Please inform.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Andrei Zobnin

    (@fiter)

    Hello! Sorry for the late reply.

    This plugin doesn’t change the way WooCommerce store and handle attributes. But it let you to use a text field instead of a select when you’re adding or editing a product attribute.

    Anyway, if you want to test performance, you can make as much products as you want using this plugin: woocommerce-product-generator

    Thread Starter itsgauravjain22

    (@itsgauravjain22)

    Could this plugin change the handling of text type global product attributes as well. The way it is now adding adding product attribute as post taxonomy. But logically, text type product attribute need to be registered as post meta. That way, we could add any text type field eg. isbn13, isbn10, books pages, upc, ean etc in a more efficient way.

    The local product attributes are just the hack, not the solution. I can’t enforce the attribute name for the data entry person. There could be the typo in product attribute name and more repetitive work to add those field names again and again.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Is it safe to use performance wise’ is closed to new replies.