Magento

Hello,
I have upgraded my system from 1.1.3 to 1.2 and now the search on frontend doesn’t work.
There appears “Your search returns no results”
Why is that so?

Go in the backend and go to cache management and select rebuild seach index. That fixed it for me

I get the following error:

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

I get the same error as well…

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

Can this be fixed?  We wanted to launch our site next week!

I had similar problem which vanished later when I enabled all cache functions.
Try this (your mileage may vary):
1 - Get a local copy of /var/cache/
2 - Delete all directories in the remote /var/cache
3 - admin / cache: enable all functions, update
Late edit: don’t do what I suggested with : including “layered navigation (beta)”
4 - rebuild search index

NOTE: of course, now you will need to manually force cache update after any chang you will do in your CSS or PHTML etc)

Also, be prepared to upload all files, like for a clean install (of course, you will need a complete backup, specially of /index.php, /.htaccess and, if any, /php.ini)

Hi Fibo,

Thanks for the response and help, I tried as you suggested but it didn’t work for me.  After reading through a few threads I found that this issue has been reported…

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

In addition, I found a manual fix that worked for my site (note: depending on the number of attributes this could be tedious).

1. For each searchable attribute, under front end properties, change the “Use in quick search” drop down menu to No.

2. After this field has been disabled for all attributes, go to system, cache management, and rebuild the search index (this should now be possible and not give the .../Abstract.php on line 351 error).

3. Now go back and change the “Use in quick search” drop down menu to Yes for each attribute.

4. Rebuild the search index again (it should now work without error).

After rebuilding the index I get this

Forbidden

You don’t have permission to access /report/ on this server.

PC Games Plus - 15 January 2009 08:37 AM

Go in the backend and go to cache management and select rebuild seach index. That fixed it for me[/quote

Thanks so much - that fixed it for me too!

 Signature 

ExtraCall.com - UK Telecommunications & VOIP | SurveySam - Worldwide market research & surveys