After v.2.3.3 updated: pagination, filtering, sorting on catalog page doesn't work

amiddio commented 4 years ago

Preconditions (*)

M2.3.3.
PHP Version 7.1.22
Chrome, Firefox

Steps to reproduce (*)

Go to catalog page
Click on pagination link (p2, p3 etc), or change product list mode, or change price rang, or change number of products display

Expected result (*)

Actual result (*)

Pagination, filtering, sorting on catalog page doesn't work

I've deleted all extensions from app/code, and theme from design/frontend. Ran "php bin/magento setup:upgrade". The issue is still exist.

It worked correct on M2.3.2. The issue appears just after update to 2.3.3. Any solution for this?

m2-assistant[bot] commented 4 years ago

Hi @amiddio. 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.

@amiddio 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] commented 4 years ago

Hi @shikhamis11. 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.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.

shikhamis11 commented 4 years ago

@magento give me 2.3-develop instance

magento-engcom-team commented 4 years ago

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

magento-engcom-team commented 4 years ago

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

shikhamis11 commented 4 years ago

@magento give me 2.3.3 instance

magento-engcom-team commented 4 years ago

Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.3.3 instance for you

magento-engcom-team commented 4 years ago

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

shikhamis11 commented 4 years ago

hi @amiddio I am not able to reproduce this issue as per your provided steps. Let me know here if you are still able to reproduce this issue or update the steps to reproduce this issue .

Thomas-gt3 commented 4 years ago

I had the same problem, the Doofinder module was the cause.

amiddio commented 4 years ago

Thank you @Thomas-gt3 for your answer. I don't use extension Doofinder.

I've got "301 Moved Permanently" on all catalog pages: /cables/network-cables./?product_list_mode=list /cables/network-cables./?product_list_dir=desc /cables/network-cables./?product_list_order=name /cables/network-cables./?p=2 ... So, Magento doesn't manage all GET variables on catalog pages. How I see...

But, it works correct on search result page: /catalogsearch/result/?q=cable /catalogsearch/result/index/?q=cable&product_list_mode=list /catalogsearch/result/index/?product_list_mode=list&q=cable&product_list_dir=asc /catalogsearch/result/index/?p=2&product_list_dir=asc&product_list_mode=list&q=cable ...

I understand it's issue on my project (not M2.3.3), but what is the reason? How can I fix it?

amiddio commented 4 years ago

I found the reason of issue. It was suffix "./" of categories and products ("Admin > Configuration > Catalog > Catalog > Search Engine Optimization"). Deleted them and regenerated Url Rewrites (used https://github.com/karliuka/m2.IndexerUrlRewrite) and the issue gone.

magento / magento2