You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
One of our clients set the product sort order for a category with core solution. After Elasticsuite was onboarded, the previously set product order was not applied to the given category.
Describe the solution you'd like
Data patch to automatically convert the previous positioning to be reflected on category pages after Elasticsuite is onboarded
Describe alternatives you've considered
Magento CLI to pull through previously set sort order of product for a given category (with confirmation question)
eg
Additional context
issue resolved for the category by running
INSERT INTO `smile_virtualcategory_catalog_category_product_position` (`category_id`, `product_id`, `store_id`, `position`)
SELECT `category_id`, `product_id`, 0 AS `store_id`, `position` + 1 AS `position`
FROM `catalog_category_product`
WHERE `category_id` = 1095
ORDER BY `position` ASC;
The text was updated successfully, but these errors were encountered:
mamsincl
changed the title
Pull previously set sort order of category product when onboarding solution
Pull previously set sort order of category products when onboarding solution
Dec 9, 2024
Is your feature request related to a problem? Please describe.
One of our clients set the product sort order for a category with core solution. After Elasticsuite was onboarded, the previously set product order was not applied to the given category.
Describe the solution you'd like
Data patch to automatically convert the previous positioning to be reflected on category pages after Elasticsuite is onboarded
Describe alternatives you've considered
Magento CLI to pull through previously set sort order of product for a given category (with confirmation question)
eg
Additional context
issue resolved for the category by running
The text was updated successfully, but these errors were encountered: