Magento2: Disable product issue with Cart Item bundle product

[sunilit42]

Preconditions (*)

1. Latest Magento
2. at least one bundle product

Steps to reproduce (*)

1. Create one bundle product with some simple product and create another simple product
2. do add to cart bundle product and simple product
3. go to cart page
4. then disable bundle product from product grid
5. check cart page again, it showing one error msg and checkout button missing https://www.screencast.com/t/ui0FVQfCm
6. then refresh again you will see checkout button
7. same thing working fine if we change status from edit product

Expected result (*)

1. edit product status from product edit or grid should be the same behavior
2. it should not show that msg and should show checkout button first time

Actual result (*)

1. https://www.screencast.com/t/ui0FVQfCm it should be directly removed and should be shown checkout button

[m2-assistant[bot]]

Hi @sunilit42. 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.3-develop instance - upcoming 2.3.x release

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

@sunilit42 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

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

[m2-assistant[bot]]

Hi @ajijshekh123. 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:

• [x] 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.

• [x] 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.

• [x] 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[ajijshekh123]

Give me @magento give me 2.3-develop instance

[magento-engcom-team]

Hi @ajijshekh123. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @ajijshekh123, here is your Magento instance.
Admin access: https://i-25484-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ajijshekh123]

I have verified this issue as per the Steps to be reproduced.
See the attached video:

[magento-engcom-team]

:white_check_mark: Confirmed by @ajijshekh123
Thank you for verifying the issue. Based on the provided information internal tickets MC-22856 were created

Issue Available: @ajijshekh123, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[magento-engcom-team]

Hi @sunilit42.

Thank you for your report and collaboration!

The related internal Jira ticket MC-25140 was closed as non-reproducible in 2.4-develop.
It means that Magento team either unable to reproduce this issue using provided _Steps to Reproduce_ from the _Description section_ on clean Magento instance or the issue has been already fixed in the scope of other tasks.

But if you still run into this problem please update or provide additional information/steps/preconditions in the _Description section_ and reopen this issue.

[bubasuma]

Internal Magento team is working on this issue right now.

[magento-engcom-team]

Hi @sunilit42.

Thank you for your report and collaboration!

The issue was fixed by Magento team.

The fix will be available with the upcoming 2.3.5 release.

[rparsi-boxycharm]

@magento-engcom-team Which commits fixed this issue?

[matthewhaworth]

Also, wondering what @rparsi-boxycharm asked.

[rparsi-boxycharm]

@matthewhaworth

Also, wondering what @rparsi-boxycharm asked.

According to magento-engcom-team:

Hi @sunilit42.

Thank you for your report and collaboration!

The issue was fixed by Magento team.

The fix will be available with the upcoming 2.3.5 release.

I searched closed pr's and commit history of various branches, can't find the commits for the fix.
I can't wait for release 2.3.5, need to find the commits magento-engcom-team made so I can create a composer patch and apply the fix(es) to my project.

[matthewhaworth]

@rparsi-boxycharm Magento said to me that it wouldn't be possible to backport a fix to 2.2.6

[rparsi-boxycharm]

@matthewhaworth I'm using 2.3.3 with the security only patch 2.3.4-p1. Can you ask Magento for the commit urls that fixes this issue in 2.3.5?
I don't get why they don't just tell us, I'm fine with back porting it myself.

[bubasuma]

Sorry guys for the delay,
Here is the commit 41565f0f7b702136668189eb5a2ecfa1d6b82d69 that fixes the issue.

[rparsi-boxycharm]

@bubasuma Thank you. Out of curiosity, why isn't it standard procedure to include commit urls whenever some says blah issue is fixed in blah magento version? It's annoying having to play conversation tag asking for this info each time, and frequently it takes months for the answer to be finally provided.