Gray out Not working if one of option of configurable Product is out of stock

[ia-gaurav]

Preconditions Magento 2.4.2 Browser Chrome/Firefox

Issue: Out of stock configurable product with custom attribute configuration Size and Fit (custom configuration with visual swatch options) is not greyed out in the front end product page.

Steps to reproduce:

1. Back End Side (admin) : Create a configurable product (Using existing, it might not reproduce). Use Size Attribute configuration. Also create a new attribute with the name Fit having visual swatch option (keep default white color to the swatches; Swatches options with under18 and 18+).
2. Save the product configuration.
3. Go to Admin: Store > Configuration >> Catalog > Inventory ; Set the option Display Out of Stock Products - Yes (This has been in the below screen shot)
4. Open the product in the front end, it loads properly (make sure cache is cleared and re-indexed in case if it is not showing in the front end.) It opens appropriately. (as shown in the screen shot below)
5. Back end - Open any one product SKU and mark it as out of stock as shown in below screen shot.
6. Again come back to the front product page and reload the product.
7. try to select the out of stock option.

Expected: If we select the size that is out of stock and then immediately relevant Fit option should be greyed out. Actual: Still the Fit option is keeping enabled and able to select

[m2-assistant[bot]]

Hi @ia-gaurav. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ia-gaurav]

@magento give me 2.4-develop instance - upcoming 2.4.x release

[magento-deployment-service[bot]]

Hi @ia-gaurav. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @ia-gaurav, here is your Magento Instance: https://7ddb6f37aa38bfd6271001e7003c1a9d-2-4-develop.instances.magento-community.engineering Admin access: https://7ddb6f37aa38bfd6271001e7003c1a9d-2-4-develop.instances.magento-community.engineering/admin_a3b5 Login: 71094d9d Password: 6f2df24249ea

[m2-assistant[bot]]

Hi @engcom-Alfa. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-Alfa Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [ ] Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again. Thanks!

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [ ] Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again. Thanks!

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-1011 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[pavel77718]

@magento I am working on this

[engcom-Delta]

Hi @ia-gaurav ,

Thanks for your reporting and collaboration. We have re-verified the issue in 2.4-develop instance , but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

1. Back End Side (admin) : Create a configurable product (Using existing, it might not reproduce). Use Size Attribute configuration. Also create a new attribute with the name Fit having visual swatch option (keep default white color to the swatches; Swatches options with under18 and 18+).
2. Save the product configuration.
3. Go to Admin: Store > Configuration >> Catalog > Inventory ; Set the option Display Out of Stock Products - Yes
4. Open the product in the front end, it loads properly (make sure cache is cleared and re-indexed in case if it is not showing in the front end.) It opens appropriately. (as shown in the screen shot below)
5. Back end - Open any one product SKU and mark it as out of stock as shown in below screen shot.
6. Again come back to the front product page and reload the product.
7. try to select the out of stock option. OOS option is grey out as expected.

Can you please re-verify and confirm if you are still facing the issue. Thanks.

[engcom-Delta]

Hi @ia-gaurav ,

This issue is being closed since it has not been updated in a long time. Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.