Magento2: Unable to change attribute type from swatch to dropdown

Created on 14 Dec 2017  路  10Comments  路  Source: magento/magento2

Preconditions

  1. Magento is installed from 2.2-develop branch
  2. Product attribute is created (Stores > Attributes > Product):
  3. Catalog Input Type for Store Owner = Visual Swatch
  4. Scope = Global
  5. Created product attribute is added to Default attribute set (Stores > Attributes > Attribute Set)

Steps to reproduce

  1. Create new configurable product based attribute from precondition
  2. Check this product on frontend - options displays as visual swatches
  3. Go to attribute and change "Catalog Input Type for Store Owner" = Dropdown
  4. Clear Cache
  5. Check product page on frontend

Expected result

Options still displays as visual swatches

Actual result

Options is shown as dropdown

Catalog Fixed in 2.2.x Fixed in 2.3.x Clear Description Confirmed Format is valid Reproduced on 2.2.x bug report

Most helpful comment

Hello Samay.
There was another thread, where somebody gave a hint.
Truncate the table eav_attribute_option_swatch and flush the cache.
For me this worked.

All 10 comments

mageconf

@eugene-shab thank you for joining. Please accept team invitation here and self-assign the issue.

Is there any workaround ?

Hello Samay.
There was another thread, where somebody gave a hint.
Truncate the table eav_attribute_option_swatch and flush the cache.
For me this worked.

I have the same problem, but I only have it for the options for manufacturer and color. If I truncate the eav_attribute_option_swatch settings I will lose all the data that still works. What is the work around?

Any update on this ?

This issue related to the - https://github.com/magento/magento2/pull/12771
Waiting for merge.

I had the same issue on 2.2.5.

I changed my custom Visual Swatches Attributes to Drop Down > flush cache > changed it again to Visual Swatches.

Now I see Visual Swatches instead of Drop Down.

Hi @alena-marchenko. Thank you for your report.
The issue has been fixed in magento/magento2#17750 by @nmalevanec in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

Was this page helpful?
0 / 5 - 0 ratings