Problem with ancestor categories and scope is All Store Views

[msloboda-macopedia]

          The problem seems  to be related with ancestor categories. If there is need to manually sort products on page with ancestor category and scope is **'All Store Views'** then to  table  `smile_virtualcategory_catalog_category_product_position` in column **'store_id' goes '0'.** 

I found that in this case store_id = 0, means admin store.

So, if certain store view is selected, other then default, then products are visible on store front.

However it is misleading behaviour, maybe when All Store Views is selected, then multiple rows should be set up in smile_virtualcategory_catalog_category_product_position table, each for separate store?

version: "smile/elasticsuite": "2.10.6"

Originally posted by @msloboda-macopedia in #2768 (comment)

[romainruaud]

Hi @msloboda-macopedia

Your description of the issue is barely not understandable for us.

Please describe exactly what you want to achieve, and what's happening. With screenshot and examples of data.

To keep it short "store_id = 0, means admin store" => nope, "store_id = 0, means all store views".

That being said, an improvement has been made in version 2.10.13 on this part : #2793

So please also try to check if the latest version could fix what you are seeing.

Regards

[msloboda-macopedia]

Hi @romainruaud,
OK, I try to clarify. Here is printscreen from smile_virtualcategory_catalog_category_product_position table

In column store_id is 0.
As You see that column is in relation with store table, where store_id = 0 means admin

So, if 'All Store Views' is selected during product order setup, then we've got 0 as store_id.
So, maybe in this scenario entries should be multiplied in smile_virtualcategory_catalog_category_product_position table. Separately for each store?

[romainruaud]

@msloboda-macopedia

1. As I said before, in the context of saving product positions "store = 0" means all store views, not "Admin". This means that these positions will be applied to all store views of your website in frontend. Except if you override these positions with a particular store view when contributing them.

2. As I asked last time, please describe exactly what you want to achieve, and what's happening. With screenshot and examples of data.

3. Please check if latest version solves your issue.

Without answers for point 2. and 3. we'll have to close your issue.

Thank you

[msloboda-macopedia]

At this point, after upgrade to version 2.10.13 it seams to be ok.