Category sort = 'position:asc' does not reflect the order set within magento categories
See original GitHub issueCurrent behavior
Currently it does not seem possible to display products within categories using the order specified in the Magento admin.
I am able to see the position number in the elastic data using Kibana. When using the new magento2-vsbridge-indexer you can see this in the categories attribute against a product.
When using the mage2vuestorefront to import data, the position number is set on extension_attributes.category_links
In either case, setting sort = ‘position:asc’ or ‘position:desc’ makes no difference to the sorting of products.
Expected behavior
When sort = ‘position:asc’ products within categories should be ordered as per the order field within magento admin
Steps to reproduce the issue
Either using postman to hit the api directly or by configuring the storefront to sort products by position:asc products will not sort by the position number. And position:desc returns products in same position as position:asc.
Can you handle fixing this bug by yourself?
- YES
- NO
Which [Release Cycle]
- This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from
develop
branch and create Pull Request2. Feature / Improvement
back todevelop
. - This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from
release
branch and create Pull Request3. Stabilisation fix
back torelease
. - This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from
hotfix
ormaster
branch and create Pull Request4. Hotfix
back tohotfix
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:22 (9 by maintainers)
Top GitHub Comments
I had it working by adding something like this to SearchAdapter.ts:
`
we are currently struggling with this exact problem - any solution yet? We are using VSF 1.12.2…