Unable to add more then 1 product to cart with persistent module disabled

[dverkade]

Preconditions

1. Magento version 2.2.2
2. Have all caching functions enabled (especially FPC cache)
3. In the config.php disable the Magento_Persistent module, set it to 0.

Steps to reproduce

1. Go to a category page and a product detail page. Add the product to the cart.
2. Go back to another product detail page and add that product to the cart as well.
3. Only the last product added to the cart is in the cart, the first product has been removed from the cart.

Expected result

1. Both products should be in the cart

Actual result

1. Only the last added product is in the cart.
2. Another session_id is created, the previous session_id is not in your cookies anymore

[ghost]

@dverkadee, thank you for your report.
We've acknowledged the issue and added to our backlog.

[m2-assistant]

Hi @Renu05. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team 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!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[Renu05]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[Renu05]

Hi @dverkade,

I have tried to reproduce the issue in the above instance Magento instance and found that this issue is not reproducible.

I have followed the steps to reproduce the issue:

1. Created a new category and two new products.
2. Assigned the product to the category.
3. Product 1 is added in cart. The product is visible in cart.
4. Now added second product in the cart. The mini cart is updated and now cart contains two products.
5. Have all caching functions enabled (especially FPC cache).

Note: Persistence Cart feature is disabled. I have tried to reproduce on local as well by making the Magento_Persistent as 0 but no luck.

As this issue is not reproducible in 2.3-develop hence closing this ticket.

[dverkade]

This issue has been verified by Magento, so reopening this so that it can be fixed.

[m2-assistant]

Hi @engcom-Bravo. 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: 👇

• 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.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

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

[engcom-Bravo]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

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

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-18021, MC-18022 were created

Issue Available: @engcom-Bravo, 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 @dverkade.

Thank you for your report and collaboration!

The issue was fixed by Magento team.