Configurable products options are not showing after upgrade 2.1.7
Linux 2.6.32-696.1.1.el6.x86_64 #1 SMP
PHP Version 7.0.19
MySql mysqlnd 5.0.12-dev
Upgrade 2.1.4 to 2.1.7
Run update command
Run upgrade command
run deploy command
Configurable products options displayed correctly
Hi @aasim110. Can you please provide the detailed steps to reproduce this issue?
I had similar problem. Try disabling Redis for cache if you have it enabled.
try this patch - change default_jobs_amount = 1;
https://github.com/magento/magento2/commit/b9ddac74c71df89e920c8f62fa59dbf3b0ddc083
@rbur0425 how to disable Redis for cache ? I have never enabled this.
@antboiko there are two attributes color and size, I have select "Catalog Input Type for Store Owner" to "Dropdown" for both attributes and it was working fine in before version, but after upgrade both attributes are showing "Swatches" on front end.
@aasim110 thank you for your feedback.
Please format this issue according to template, with exact steps to reproduce, actual result and expected result.
Please also provide additional information:
Upgrade 2.1.4 to 2.1.7
For upgrade we are using following steps for upgrade
We are using
Hi!
I'm new to Magento, and how could I disable Reddis or apply that default_jobs_amount = 1 fix?
Thanks in advance!
Temperory solution is replace old version default swatch module "vendor/magento/module-swatches" with new one.
it is working fine for me.
Hi @aasim110 do you mean, in order to fix this issue, you have replaced the NEW module (that comes with the patch) with the OLD one?
@btwq Yes exactly!!!
@aasim110 Temperory solution is replace old version default swatch module "vendor/magento/module-swatches" with new one.
I have hit the exact same problem. Could you let me know how to replace it with the new one? Where is the new one?
@mindaji get old module and replace with new one
for example : you had 2.1.5 version before upgrade(2.1.7), then copy files from 2.1.5 "vendor/magento/module-swatches" to latest version files
Note : don't replace files, first remove all files from 2.1.7 and then add 2.1.5 module files.
Dear Sir or Madam:
Thanks a lot!
From: Aasim [mailto:[email protected]]
Sent: Thursday, August 10, 2017 1:40 AM
To: magento/magento2 magento2@noreply.github.com
Cc: Minda Ji mji@dataclub.com; Mention mention@noreply.github.com
Subject: Re: [magento/magento2] Configurable products options are not showing after upgrade 2.1.7 (#9833)
@mindajihttps://github.com/mindaji get old module and replace with new one
for example : you had 2.1.5 version before upgrade(2.1.7), then copy files from 2.1.5 "vendor/magento/module-swatches" to latest version files
Note : don't replace files, remove all files from 2.1.7 and then add 2.1.5 module files.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/magento/magento2/issues/9833#issuecomment-321489038, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AdULhmpxfbwpsscr-680J_4kVsLl4VS3ks5sWsHCgaJpZM4NuDGM.
@aasim110, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.
We tested the issue on 2.1.9
@mindaji @btwq @rbur0425 I have fixed issue after Flushing "eav_attribute_option_swatch" table entries corresponding to the attribute (all of them, not just specific to single product or option).
I have tried this on 2.1.7, 2.1.9 and 2.2.1 and its working fine for all.
aasim110: Could you let us know how to flush "eav_attribute_option_swatch"?
@aasim110 could you clarify "flushing 'eav_attribute_option_swatch' table entries corresponding to the attribute (all of them,not just specific to single product or option)". Did truncate the entire table or only certain columns/values?
@jmtakahashi truncate the entire table except image entries.
Most helpful comment
@mindaji @btwq @rbur0425 I have fixed issue after Flushing "eav_attribute_option_swatch" table entries corresponding to the attribute (all of them, not just specific to single product or option).
I have tried this on 2.1.7, 2.1.9 and 2.2.1 and its working fine for all.