-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Wrong order of products. #2868
Comments
I'm fixing this one |
Thanks, great job @Jensderond ! |
The problem we have is not because of some logic. The final_price field in elastic is null, that's why sort order is broken in some cases. @lukeromanowicz do you know a reason why some product does not have a final_price? |
IF ES product doesn't contain final_price and this is an unmodified result from ES then I would look for the root cause in the indexer. I'll try to take a look at that. |
I'd suggest to run full reindex and check it out. The |
@alinadivante can you please reimport and test this issue once again/ |
@pkarw I still have a problem with reindex/reimport, even if I made sure that the test_fullreindex.sh script is properly configured.. |
I've checked it and the initial problem is seemingly fixed once and for all. The only issues I could find were related to cases of configurable product with let's say https://www.dropbox.com/s/rfgigksmxl1il62/Screenshot%202019-09-12%2021.47.39.png?dl=0 SKU: WB03 |
Current behavior
If u set Sort by Price: Low to high and than you change category, you will see your saved sort selection, but order of the products will be the default.
Expected behavior
After changing the category, the previous sorting selection shouldn't be saved or it should be applied.
Steps to reproduce the issue
Repository
Can you handle fixing this bug by yourself?
Which Release Cycle state this refers to? Info for developer.
Pick one option.
develop
branch and create Pull Request2. Feature / Improvement
back todevelop
.release
branch and create Pull Request3. Stabilisation fix
back torelease
.hotfix
ormaster
branch and create Pull Request4. Hotfix
back tohotfix
.Environment details
Additional information
The text was updated successfully, but these errors were encountered: