Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #15627: Product order in category changed in Magento 2.2.4 #15629

Merged
merged 1 commit into from
Jun 22, 2018
Merged

Fix #15627: Product order in category changed in Magento 2.2.4 #15629

merged 1 commit into from
Jun 22, 2018

Conversation

dverkade
Copy link
Member

@dverkade dverkade commented May 31, 2018

Description

This PR is a fix for issue #15627 where the default sorting behaviour of Magento was changed in Magento 2.2.4.

Fixed Issues

  1. Product order in category changed after update to Magento 2.2.4 #15627: Product order in category changed after update to Magento 2.2.4

Manual testing scenarios

  1. Have a category in Magento with several products in it, all have the position in the category set to the value 0
  2. The default sort order should be set to position
  3. View the category. The product with the highest entity_id (newest product) should be shown first.

… of Magento was changed in Magento 2.2.4.
@magento-cicd2
Copy link
Contributor

magento-cicd2 commented May 31, 2018

CLA assistant check
All committers have signed the CLA.

@ishakhsuvarov
Copy link
Contributor

Hi @dverkade
Do you think this fix would not cause #11139 to reproduce again?

@dverkade
Copy link
Member Author

dverkade commented Jun 19, 2018

Hi @ishakhsuvarov,

Thank you for your reply. This PR will not change the fixes introduced by #11139 which will still be there. This PR removes an unnecessary extra sort order introduced by #11139. I have also filed a bug report for this behaviour under #15626 as you can see the sort order for entity_id is added multiple times now and this changed the default sorting behaviour of Magento. The default sorting of entity_id descending is already always added by Magento, so no need to specify it again with the fixes introduced for #11139.

@ishakhsuvarov
Copy link
Contributor

@dverkade Seems legit to me. Thank you for the detailed explanation.

@magento-engcom-team
Copy link
Contributor

Hi @dverkade. Thank you for your contribution.
Changes from your Pull Request will be available with the upcoming 2.2.6 release.

Please, consider to port this solution to 2.3 release line.
You may use Porting tool to port commits automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants