mass actions

[airbone42]

check how to deal with mass actions and importers.

is model save called?

[avstudnitz]

It's not. Mass Action uses Mage_Catalog_Model_Resource_Product_Action::updateAttributes, ImportExport uses it's own resource model as well. Perhaps you can jump into indexer processing as those are called in all (useful) cases.

[airbone42]

Mage_Catalog_Model_Resource_Product_Action::updateAttributes doesn't throw any events, where we could hook into, but indexer processing is only called if it's not set to manual, which is the case on a lot of stores which are deployed to prevent heavy database operation during business hours. :(
So to really track the changes we would have to rewrite Mage_Catalog_Model_Resource_Product_Action and maybe even other resource models, like you mentioned for ImportExport.

Anyway we wanted to add a logging for triggering index and cache changes, but that would only show that something might have happened, not really what changed.

[Schrank]

we can log the indexing, when we hook into the predispatch event, and just log the $_POST content.

If you ask me, we are not interessted in changes in indexes and caches...