http://www.magentocommerce.com/bug-tracking/ en MagentoCommerce Copyright {gmt_date format="%Y"} {gmt_date format="%Y-%m-%dT%H:%i:%s%Q"} http://www.magentocommerce.com/bug-tracking/issue?issue=4631 Posted: 2008-12-31 15:06:24
Category: Search
Version: 1.2.0.1
Priority: urgent
Status: closed
Reported By: hirshy

Search wasn't working properly so under "Cache Management" I clicked on "Rebuild Index" and got the following error:

Fatal error: Call to a member function setAttribute() on a non-object in /home/jsularsk/public_html/app/code/core/Mage/Eav/Model/Entity/Attribute/Abstract.php on line 351

I have found various posts regarding this issue where many users are having the same problem:
http://www.magentocommerce.com/boards/viewthread/27151/
http://www.magentocommerce.com/boards/viewthread/27061/
http://www.magentocommerce.com/boards/viewthread/27076/

Auto Complete in search is now showing results preceded by a number and when you click search it says there are no results. I wouldn't mind even shutting off the entire search module for the site until this is fixed but this has proven to be not so simple.

---

]]> #1 / Comment by _Jimbo

I had the same error message,
and decided to delete my whole Product Stock, for there seems to any database issue.
that was impossible, an error that "store_id" coulld not be found in the fieldlist.
I had to unassign all Products from the main website, Then I could delete them, and was able to rebuild the Index without errors.
perhaps It's worth a try to unassign the whole stock, and reassign it lateron in backend under "update Attributes."
Regards, Jimbo]]> #2 / Comment by hirshy

Thanks Jimbo,

I tried what you said. In "Manage Products" I selected all products and then in "Actions" selected "Update Attributes" and then removed all products from the main store. When I refreshed the cache and then tried rebuilding the index it worked. When I reassigned the products afterward the error happened again. I even tried to only assign one product and I still got the same error when trying to rebuild the index.

Hirshy]]> #3 / Comment by cycore

In my case, this issue was caused by a custom attribute using the multiselect type. After deleting the attribute, the rebuild process worked fine.

The usesSource() method returns true for these multiselect attributes, but the getSource() method does not return anything.]]> #4 / Comment by GenericWhiteGuy

Confirmed that this error occurs if an attribute is set for "Use in Quicksearch" and is a multiple select. Setting "use in quicksearch" removes the error, obviously because it isn't being indexed anymore.

My observations:

1. If a multi-select is enabled for quick search and is available to any products there will be an error.
2. Deleting products or attributes and re-adding them will result in the same error once you create an attribute with Multiple Select and enable quicksearch.

Anybody have a temporary workaround?]]> #5 / Comment by jogide

Ok, the same problem.

@genericwhiteguy :

I have modified the attributes that are part of grouped attributes. In the tab "use quick search" I select "not".

The rebuild button has worked at the first.

The attributes of configurable products can not be used for the mini search ! Only des-select and rebuild.]]> #6 / Comment by thE_iNviNciblE

i can successful rebuild the search index, but i can't search on the frontend.
i also have tried to disable the quicksearch functions... of the dropdown list.... and disabeled the functions of "filter layout"]]> #7 / Comment by Jesse Stewart

Same issue. I was getting this same error editing products and rebuilding the search index.

I changed all attributes to not be in advanced search or quick search. This made the errors go away.
I reset one of the drop-down attributes and NO ERRORS when editing products.
I reset one of the muti-select attributes and NO ERRORS when editing products.

Rebuilding index and ERRORS.
Disabled the search on the multi-select and NO ERRORS.

Moral of the story - Multiple select can not be searchable without getting errors. Thanks to everyone here that helped me get to that conclusion.]]> #8 / Comment by janhoy

Confirmed that a workaround is to disable QuickSearch (no need to disable advanced), then rebuild index.
However, I have geography as one of the attribuets, and it really needs to be searchable, so a fix is highly needed!

Related question: I also need search on category names to bring up relevant products. Where can I enable category names in QuickSearch]]> #9 / Comment by thE_iNviNciblE

Hi Dev-team

maybe this issue also fixed:

http://www.magentocommerce.com/bug-tracking/issue?issue=4693

i've also tried to disable all attribute from searchable (only description) and also the error...
the search index can be build successful at may installation.]]> #10 / Comment by Business Feet

How can this be resolved when everyone is still getting the same errors - if it is resolved where is teh fix, come on magento team - a little bit of communication isn't too much to ask is it?]]> #11 / Comment by rrroulio

exact, where is the solution? Disable quick search in attributes to rebuild index is not a solution. The problem is in the core, it needs a real attention]]> #12 / Comment by bcelenza

I'm still looking for a solution to this issue. What build is this scheduled to be a part of? Is there a patch we can apply in the meantime?]]> #13 / Comment by b*rock

I'm getting the same error runing v1.2.0.2]]> #14 / Comment by flufftronix

Another install with the error here on 1.2.0.2]]> #15 / Comment by cradossk

+1]]> #16 / Comment by DaymoH

me too]]> #17 / Comment by ptjedi

I have this error too - No frontend quick search and can't rebuild search index... This is in need of proper attention. Don't know why this bug was classified as "resolved" when it is not.]]> #18 / Comment by Vegard

Hi
See post number 7 from Jesse Stewart. This is the workaround and it did work for me..]]> #19 / Comment by Mage4Frank

Confirm on post number 7. Make multiselect attributes not searchable within quicksearch. To find those attributes, I use underscore (_) to name my attributes, use this sql.

SELECT *
FROM `eav_attribute`
WHERE `attribute_code` RLIKE ?^_?
AND `is_user_defined` =1
AND `frontend_input`=?multiselect?
LIMIT 0 , 30

To set to not searchable: Use at own risk!

UPDATE `eav_attribute` SET `is_searchable` = 0
WHERE `attribute_code` RLIKE ?^_?
AND `is_user_defined` = 1
AND `frontend_input`=?multiselect?

Now you can rebuild search index.

Set searchable at quicksearch again: Use at own risk!

UPDATE `eav_attribute` SET `is_searchable` = 1
WHERE `attribute_code` RLIKE ?^_?
AND `is_user_defined` = 1
AND `frontend_input`=?multiselect?]]> #20 / Comment by MichalL

+1]]> #21 / Comment by radoslawg

This is indeed not fixed! On the bright side, if I disable from search my multiselect attribute - I can rebuild the index. I'm running 1.2.0.3 .
Can someone reopen this issue?]]> #22 / Comment by Unirgy

I've uploaded fix here:
http://www.magentocommerce.com/boards/viewthread/27061/]]> #23 / Comment by Michael

@radoslawg: the issue is not closed yet. there no need to reopen it]]> #24 / Comment by rrroulio

yesssssssssssssss! i can rebuild search index !
like as post 22, the solution is found with the fix posted by mbguy
take a look Varien !]]> #25 / Comment by rrroulio

So, it works, but i still have the same problem with the "browse by" sub menu (don't display since 1.2 version)???]]> #26 / Comment by Magento Team

Hello hirshy,

This issue was fixed. The changes will be available in the next bugfix release.

Thank you.]]> #27 / Comment by bcelenza

Thanks for the update Magento Team, looking forward to it!]]>