Layered navigation module started acting funny

[the.rampage.rado]

Hi guys/gals, if somebody can give an idea it will be greatly appreciated.

I run multistore installation and I have 6 shops.

Everything was working OK until recently - all products were displayed properly using the LNM filters in all shops. I'm sure because I did lot of work with the color filter in the additional shops where I added many clothing items and all of them have color combinations.

Yesterday I noticed that only the color filter does not display in all non default shops. Then I saw that this applies for size too (generally all attribute filters, only the feature filters are visible in the addon shops).

Here are the things I tried:
- reindex all LNM indexes

- reinstall the module

- I had filter templates based on each shop - the issue presented with this setup. Then I removed them and made new template for all shops and all categories - no bueno.

- in despair tried changing the button type of the color filter - as expected no effect 🙂

- checked all shop associations - in attributes (group and each attribute), in LNM - everything is associated with every shop.

- tried regenerating the indexes in all shops context and in each one context - no affect (even not sure if LNM cares about this).

When reindexing I noticed that the price index takes much longer than the attribute index and this led me to check the code and then the db. This is where I think I have some issue. In table XXX_layered_product_attribute I only have records with shop id 1.

Because I use the modded version of the module that was part once of PS1.6.1.24 and comes with Warehouse theme I use I compared the indexAttribute function and they are 1:1 with the most current TB version of the module. XXX_layered_price_index has all shop ids.

Any input will be greatly appreciated! Am I missing something?

As this is my production instance and I can't replicate this issue on my test setup I am unable to test with TB native module currently.

TB version: edge as of today
 

[the.rampage.rado]

@datakick can you reproduce the following steps?

1. Install native thirty bees layered module in multistore.

2. During installation all indexes are obviously build and table XXX_layered_product_attribute is populated correctly with all combinations for all shops

3. Rebuild attribute index with the button.

Expected result:
1. XXX_layered_product_attribute should contain all combinations for all shops (depending on association of course).

Current result with edge test installation:

1. XXX_layered_product_attribute contain only combinations for shop id 1.

This is with the native thirty bees and uninstalled the modded module from above (which uses the same table names) in my test instance where I have only 2 shops.

If I click on the button I have to reinstall the module to reindex and never touch this button. All other buttons seem to work correctly (or at least they don't mess anything I can see).