The site I'm working on, is using a template that seems the default one but I've checked that has some hardcoded pieaces of code. One of them had comment out the code that echo the layered navigation search... so that was the problem

I'm using a attribute called "Object type" set as dropdown.
That attribute is set as "Use In layered navigation" = filtered (I've tried either with "with results" and "no results")

The attribute is in a attribute set.
The elements of the subcategories that I want to show the layered navigation are all of the same attribute set.
The elements of that subcategories have the attribute "Object type" always set (it's not left blank).

On categories not set as anchor it shows the navigation menu displaying the sub-categories.
On categories set as anchor it displays nothing.

I've tried this script solutions but it doesn't solve my problem.

Is it possible to make any echo of variables somewhere (or looking in the database) to find where's the problem?

If you trace what Magento actually does during indexing, it creates a large transaction in PHP by hammering the database then pushes this huge transaction (per product) to the database. Its an immense query and although they've optimized it a bit, its less than forgiving.
Magento 1.1.4 handles post-indexed sites (I index on my over-specced workstation before pushing the database) better than its predecessor but changes to the code mean 1.1.4 fudges badger and I've not really had many requests to drag it on; which is either down to people no updating, or people not needing it, hard to say which.

I've got a half eaten article about setup requirements for magento sat in my drafts-bin, with any luck I'll shed some light on the nicest looking hungry hungry hippo of an ecommerce platform available for free )

All of the above freeze in 'Processing' mode - presumably a server timeout (semi-dedicated at Gigapros who allow up to 10% CPU usage.

Interestingly essentially the same site but with 60,000 products works fine on Magento 1.3 using Badger, but at a different shared host...

Once again cheers very much Chris

I have these three files used:

cache.php
cache2.php
cache_vycisti.php

These files are working properly for a Store View 1.

Now I would like to delete from the Store View 2 cache.

Which file should I change?
How do I find the line about Store ID query?

Thank you very much !

Xeon2901: Hey just change the "configurable" to match your store ID and run the script. A few people using the PHPCLI version have made copies of the script and run it as a CRON job ($STOREID = '1';)
Another method is to look at the first CLI version I wrote which uses ARGS from the command line.
Glad to see its a real message; I saw the username in my email and expected to be sold viagra ;o)

thank you for this script !

I have another question:

How to delete the cache on my other Store Views?

English: Store ID1 (works)
Spanish: Store ID 2 (not)
France: Strore ID 3 (not)

Do I need to change something in the script?
If so, what exactly?

Thank you!

Now I'am with version 1.4.1 and I got the same error than James:

The Catalog Search Index is always at Processing. When I force a refresh, I got a timeout error from my webhost. It's the same kind of problem than before, but not on layered navigation but on fulltext search index...

Can you help?

Thanks

I've been doing some testing with 1.4 . I've imported my 18,000 products, and you're correct it looks like it's able to handle reindexing product attributes, but it always times out when I try to rebuild catalog product fulltext search index.

Just for reference anyway, it may be something you might to look at in future. Looking at the table, it looks like it gets through about 5500 records before it stops.

Thanks

James

I tried the web version (wrapper), but i just have the header "Layered Navigation Refresh From Browser" and nothing else. What am i doing wrong?

Thanks for the great script. Works flawlessly!!
--
James

One question: We have more than one Store (end storeid)

If I use

Mage::getSingleton('catalogindex/indexer')->plainReindex($i, null, null)

(last param null instead of $sx

will I create LN for all store?

Thanks.

thanks in advance

If you dont have full ssh you can usually get a relatively good idea using http://www.wormly.com/ as its a PHP script. Handy for monitoring memory spikes.

I've stuck a call-out onto twitter, if anyones still having issues regarding layered indices using too much mem/timing out let me know and I'll have a poke. Otherwise I'll be assuming in the meantime its resolved as of Magento 1.4.1.

Thanks