Sie sind hier: Neuigkeiten » 2009 » January
Magento Bug within search index
23.01.2009Fatal error: Call to a member function setAttribute() on a non-object in /kunden/lemonzoo.net/dev/axcom/shop/magento/app/code/core/Mage/Eav/Model/Entity/Attribute/Abstract.php on line 351
I had the same Problem. Try this. It works for me.
Make all your custom multiselect attributes non-searchable within quicksearch. Multiselect attributes are all attributes that have ‘Multiple select’ as their ‘Input Type’. You can leave ‘Use in advanced search’ as it is, as it works for me.
Now go to see the magentocommerce Attribute Properties (/index.php/admin/admin/catalog_product_attribute/) and choose ‘no’ at ‘Use in quick search’ at all attributes that are ‘Multiple select”.
Cause I have plently of custom attributes, both select and multiselect and searchable and not searchable, I use sql to find and to change them.
All my custom attributes start with an underscore (_) so I can easily detect and change them by sql. Use at own risk!
To find my custom multiselect attributes:
SELECT *
FROM `eav_attribute`
WHERE `attribute_code` RLIKE ‘^_’
AND `is_user_defined` =1
AND `frontend_input`=’multiselect’
LIMIT 0 , 30
To change my custom multiselect attributes:
UPDATE `eav_attribute` SET `is_searchable` = 0
WHERE `attribute_code` RLIKE ‘^_’
AND `is_user_defined` = 1
AND `frontend_input`=’multiselect’
Now you can ‘Rebuild’ your ‘Search Index’ (/index.php/admin/admin/system_cache/)
To make my custom multiselect attributes searchable again:
UPDATE `eav_attribute` SET `is_searchable` = 1
WHERE `attribute_code` RLIKE ‘^_’
AND `is_user_defined` = 1
AND `frontend_input`=’multiselect’
