Color attribute taking swatch instead of Drop down option for configurable options,

[vishveskrish]

Preconditions

1. Magento: 2.1.6

Steps to reproduce

1. Login to admin-panel and go to the Product >> Attributes.
2. Created color attribute with Catalog Input Type for Store Owner to "Drop down"
3. Go to the front-end and open any configurable product with COLOR options.

Expected result

1. It should display Dropdown select box.

Actual result

1. It is showing swatch.

Kindly see screenshots.

[elisabethesbjornsson-vaimo]

I am also experiencing this issue, after upgrade from 2.1.4 to 2.1.6.

[lingwooc]

+1 I had it working originally as a dropdown. Then changed it to a swatch, now I can't go back to a dropdown. The setting saves but the front end ignores it. I assume is is because the extra attributes are created for the options when it is turned into a swatch, then not removed. No amount of cache clearing fixes it.

[gclift]

+1 Also had this issue after switching to swatch then back to dropdown. When the product detail page is showing, we're seeing markup with 'swatch-input'. Note, we upgraded from Magento 1.9 to Magento 2.1.6 and imported the data using the magento import tool. It was appearing fine as a drop down until we changed the "Catalog Input Type for Store Owner" from dropdown to Text Swatch.

Markup that appeared after switching to text swatch, and remained after switching back to dropdown:
input class="swatch-input super-attribute-select" name="super_attribute[133]" type="text" value="" data-selector="super_attribute[133]" data-validate="{required:true}" aria-required="true" aria-invalid="true" style="visibility: hidden; position:absolute; left:-1000px"

[vishveskrish]

Any one get resolution ?

[gclift]

I traced the code back to the isProductHasSwatchAttribute in the Magento\Swatches\Block\Product\Renderer\Configurable class. It's using the SwatchAttributesProvider class to check for swatch data.

It looks like there is some leftover data in the eav_attribute_option_swatch table after switching back to the dropdown. Once I cleaned out the swatch values that were created when we switched to the text swatch, it worked as expected again.

To see if there is data, and get the swatch_ids, use this sql query:
Note: Change YOUR_ATTRIBUTE_ID to the id of your attribute.
SQL

SELECT o.option_id, o.attribute_id, s.swatch_id
FROM eav_attribute_option AS o
JOIN eav_attribute_option_swatch AS s ON(o.option_id = s.option_id)
WHERE o.attribute_id = YOUR_ATTRIBUTE_ID
ORDER BY s.swatch_id ASC;

Having this issue also on 2.1.7.

[imsergiobernal]

Me too, same issue in 2.1.7

[mayankzalavadia]

We are also facing the same issues on Magento 2.1.7. If anyone finds a solution for this issue then please share it with all.

[lingwooc]

@gclift gave a manual solution above. It will need some db editing.

[oleg-onufer]

Hi @vishveskrish.
Thanks for reporting this issue.
Internal ticket MAGETWO-70321 was created.

[sdotsuk]

Using your preferred database editor, navigate and find the table eav_attribute_option_swatch

Magento will store a row for each of the swatches you have configured in the Magento Admin.
Pay attention to the option_id select each row you want to remove as a swatch not forgetting to remove any other associated rows which contain the same option_id.

Once deleted. Head over to your Magento admin panel, clear the magento cache and static file cache.

I was able to solve my issue in 5 minutes. I hope this helps somebody else

[gboz17]

Thanks @sanjeshsodha !!

I can confirm this works.