Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

on search error #47

Closed
SiddiqueAhmad opened this issue Jan 15, 2016 · 13 comments
Closed

on search error #47

SiddiqueAhmad opened this issue Jan 15, 2016 · 13 comments

Comments

@SiddiqueAhmad
Copy link

Fatal error: Call to undefined method Mage_Catalog_Model_Resource_Product_Collection::isSpellchecked() in /home/esajee/public_html/esajee.com/app/code/community/Smile/ElasticSearch/Block/Catalogsearch/Result.php on line 31

it was running fine before, not sure what we change in setting of attributes that this error came

@romainruaud
Copy link
Contributor

This can happen when ES is not running, this is due to the fact that Magento falls back to it's standard search engine, and then uses its native Collection model which does not have this method.

Are you still facing the issue ?

@EsajeeSolutions
Copy link

i am glad you replied, no it was solved, only the elastic search was not running

@romainruaud
Copy link
Contributor

Fine,

then I close this issue.

Thank you for submitting it.

@mobilizer
Copy link

I suggested a pull request to solve the error when ES server is down, unavailable or disabled in Magento config: #88
(I think ES server unavailability should be handled.)

@kirmorozov
Copy link

ES server unavailability should be handled, by making it available.
There are cases when 70-80 of sales are going through search.
Such fallback will just crash the system(put mysql down due to overload).
There is no point of doing such failover, its like redis, part of system.

@mobilizer
Copy link

mobilizer commented Oct 27, 2016

Two points:
1.) I think it is no good idea to premise the availability of the search server for the functionality of the complete system. (E.g. See the massive DDOS attack last week.)
2.) Current implementation has no fallback handling. And the error is unhandled and can be avoided relatively simple. (Yes.. for high volume sites, search should be just disabled if ES server is away... But current implementation already does a fallback to default Magento catalogsearch, but fails on block output. So the workload is already there.)

@kirmorozov
Copy link

1.) Just scale your cluster, make it unbreakable. Depends on reason of failure. Make your system successful to attract DDoS
2.) Looks like you want to index data twice or have out-dated index.

@mobilizer
Copy link

@kirmorozov Have you looked at the source lines generating the error? Better keeping a case with an unhandled "undefined methode" error? Really?

@ZaneCEO
Copy link

ZaneCEO commented Sep 18, 2019

Hi guys,
I need to switch back to Magento MySQL search due to project needs. We will probably go back to ES in the future, but, still, for now I need Magento basic search.

I tired to select MySQL from Search Engine, but I get this exact error on isSpellchecked(). Can we do something about it?

@riconeitzel
Copy link

@ZaneCEO #88 implement this fix!

@ZaneCEO
Copy link

ZaneCEO commented Oct 15, 2019

@riconeitzel Thanks for your reply! Yet, #88 is not merged yet, I'm I wrong? If so: which tag/release has it?

@riconeitzel
Copy link

riconeitzel commented Oct 15, 2019 via email

@ZaneCEO
Copy link

ZaneCEO commented Oct 15, 2019

Thanks Rico, I will!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants