I’m having trouble with product collections in Magento 1.7. When I use addAttributeToSelect("*"), the final_price is set but it’s not accurate. The observers for catalog_product_get_final_price don’t run, and custom attributes aren’t processed properly.
Here’s what I’ve noticed:
Collection items have a final_price from flat tables, but it’s wrong because observers haven’t run.
The getFinalPrice function in Mage_Catalog_Model_Product just returns the stored value instead of recalculating.
Custom attributes (stored as JSON) aren’t decoded into objects like they are when loading products directly.
Is there a way to make collection items behave like individually loaded products? I want to ensure the data matches in format and value. I know I could load each product individually, but that’s not always possible with third-party software.
Any ideas on how to fix this? It’s causing issues with pricing and custom attribute handling.
hey there, interesting problem! have you considered using the catalog/product_flat observer? it might help trigger those price calculations. what about creating a custom event for collections? that could let you process attributes the way you want. just brainstorming here - whats your thoughts on these ideas?
yo, i feel ur pain with magento collections. have u tried using the afterLoad() method on the collection? u could override it to trigger price recalculation and attribute processing. might be worth a shot. also, check out the _afterLoad() method in Mage_Eav_Model_Entity_Collection_Abstract. could be useful for custom attribute stuff.
This is a common challenge with Magento 1.x collections. The behavior you’re experiencing is due to the way Magento optimizes collection loading for performance. To get accurate prices and fully processed attributes, you might need to implement a custom solution.
One approach is to create a helper method that processes collection items individually. This method could iterate through the collection, load each product fully, and update the collection item with the processed data. While this isn’t as efficient as pure collection loading, it ensures accuracy.
Alternatively, you could look into extending the collection class to trigger the necessary events and processing during load. This is more complex but could provide a more seamless solution.
For custom attributes stored as JSON, you might need to create an after-load observer that decodes these attributes for collection items. This would mimic the behavior of individually loaded products.
Remember, any solution will likely impact performance, so be sure to implement caching mechanisms where possible.