Magento2: Change catalog_category_view.xml to 1column return zero products with elastic search on 2.3.2

[ron-jomashop]

Preconditions (*)

1. Magento 2.3.2
2. Enabled elastic search 2

Steps to reproduce (*)

1. Extend catalog_category_view.xml to 1column in a new theme
2. Enable elastic search 2
3. Reindex all indexes
4. Go to any category pages and it will not show any products

Expected result (*)

1. Should have products

Actual result (*)

1. It does not have any products showing

[m2-assistant[bot]]

Hi @ron-jomashop. 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.

@ron-jomashop 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.

[ron-jomashop]

I cannot reproduce this in Magento 2 instance because this requires change of the theme and enable elastic search.

[m2-assistant[bot]]

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: :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.

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

Hi, @ron-jomashop ! I can't reproduce this issue on fresh 2.3-develop branch.

Manual testing scenario:
1.Extend catalog_category_view.xml to 1column in a luma theme
2.Enable elastic search 2
3.Reindex all indexes
4.Cache flush
5.Go to any category pages

If in your case used custom theme please refer to the Community Forums or the Magento Stack Exchange, for advice or general discussion about this issue.

Thank for your report!

[ron-jomashop]

Can you show me an image with 1 column category page working in your local? Because I have tested with Magento 2.3.2 repository and it does not work.

With 2 column:

With 1 column:

[ron-jomashop]

@engcom-Bravo All you need is to enable the category to 1 column with elasticsearch 2 enable and it should reproduce the bug.

[engcom-Bravo]

@ron-jomashop
I did it on 2.3.2 and the result is the same as on 2.3-develop:
With 2 column:

With 1 column:
Page is blank(no any exceptions and errors):

[engcom-Bravo]

@ron-jomashop okay, i don't like this behavior and i confirm this issue.
Thank for contributing!

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-18255 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._

[hostep]

Since this issue was confirmed, I think the status should be Open instead of Closed, right?

[hostep]

@engcom-Bravo: can you add those labels again which got automatically removed?

[engcom-Bravo]

@hostep , thanks for contributing! that was my mistake.

[m2-assistant[bot]]

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: :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.

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

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

[ron-jomashop]

@ron-jomashop okay, i don't like this behavior and i confirm this issue.
Thank for contributing!

Thanks for rechecking. The elastic search does have many bugs currently. I have some patches in order to make it work that's why I can bypass the blank page.

[m2-assistant[bot]]

Hi @ashutoshwebkul. 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 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. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[ashutoshwebkul]

I think this issue is fixed since I am not able to reproduce it then why it is still in open state

[sedax90]

I've the same problem on 2.3.3... issue is still open

[sdzhepa]

The related internal Jira ticket MC-18255, MC-23842 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 on the latest 2.4-develop please create new Issue with updated information/steps/preconditions in the _Description section_.