We've created an additional indexer that is started by using the backend indexer functions. We have flat tables enabled. We have multiple storeviews that correspond to different languages.

The following code is an excerpt from the indexer code.

public function rebuildIndex ($productIds) {
  $stores = Mage::app()->getStores();
  foreach ($stores AS $store) {
    $products = Mage::getModel('catalog/product')
      ->addAttributeToFilter('status', 1)
      ->addAttributeToFilter('visibility', array ('in' => array (Mage_Catalog_Model_Product_Visibility::VISIBILITY_IN_SEARCH, Mage_Catalog_Model_Product_Visibility::VISIBILITY_BOTH)))

The problem is that for the second and third store, the products loaded use the language of the first storeview.

We've tried finding out what the problem is. So far, we've seen that when using flat tables, the product flat tables created are these:

  • catalog_product_flat_1
  • catalog_product_flat_2
  • catalog_product_flat_3

The number at the end corresponds to the storeview (and therefor the language). However, in all cases, the generated SELECT statement selects from the first table, making the language of the products loaded in all 3 storeviews the language of the first storeview.

We can't disable flat tables (which we tried, and that fixes the problem). Is there any way to load the products for each of the storeviews?

  • Try adding addStoreFilter() to your product collection after you set the store. I've not seen setStore($store) used before, but I have seen setStoreId($store->getId()) - Not sure if there's gonna be a difference.
    – pspahn
    Commented Aug 1, 2014 at 18:05
  • Added setStoreId(...) followed by addStoreFilter() to the building of the collection. No change.
    – 0xCAFEBABE
    Commented Aug 4, 2014 at 6:14
  • @0xCAFEBABE were you able to solve this problem? If so, how?
    – 7ochem
    Commented Mar 8, 2016 at 13:41
  • 5
    We determined it to be a problem of the flat tables. We inserted a Mage::unregister('_resource_singleton/catalog/product_flat'); right before doing the collection gathering, so the indexing would work around the flat tables. It's usually executed from the command line anyway, so performance wasn't critical.
    – 0xCAFEBABE
    Commented Mar 9, 2016 at 8:03
  • @0xCAFEBABE, thanks, this solution works fine
    – intheweb
    Commented Jul 6, 2018 at 7:28

1 Answer 1


I too was facing the same issue.

Mage::unregister('_resource_singleton/catalog/product_flat'); didn't do the job for me.

I was able to solve it by setting the current context to Admin using:


When you look into _construct method inside app/code/core/Mage/Catalog/Model/Resource/Product/Collection.php

You can see that it's initializing catalog/product_flat only when isEnabledFlat returns true.

And isEnabledFlat would return false when we are in the admin context

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.