You can clone with
HTTPS or Subversion.
The more I think about the unwillingness to repair a major flaw in Magento the more I think about migrating to another platform. I've worked with so many ecommerce platforms that have zero problems with one of the most important storefront features "SEARCH". I've also watch so many customers search a site and leave the site because a search never presented the actually product the customer was looking for but the store possessed.... That is called a flaw!
Now I understand it's quite an undertaking, but putting it off or relying of someone else to provide such capabilities is not the solution either. I say we fix the issue and make it a top priority. NOW before 2.0 is released.
This is a major issue with magento and if you haven't noticed it yet then you haven't run a store... Period
100% on target - should be top priority.
I agree that the search is very poor at best. We have been using Google SiteSearch, which has been an acceptable alternative, although we do not have the control that we would like. I think most of that can be overcome with more code. It would be very nice to have a free solution to this basic problem.
+1 for this being top priority. Please give the best shopping cart out there the best search.
For Magento 2.0 we're planning on modularizing search and making it easier to customize. For search improvement it's already a high priority ( with a lot of items I'm pushing for ) but there's still debate on when and how those improvements will release. Please keep commenting and specifically state what you want as highest search priority. That'll help us refine prioritization and how we could release in light of other priorities.
So far I see ( 1 for better search results; 1 for more search control ); please get others to comment/weigh in and provide specifics on their top search item to address.
@ryansun currently we're planning on mysql search for CE and SOLR for EE; with hooks for the community to easily support other search engines like sphinx, etc.
@gfxguru when you say more accurate search results do you have something in mind specifically ( based on my research/understanding it's 2 things - weighting control & search reports to identify search terms with no results; i.e. identify the case you're describing with weighting control to address/fix ).
Chuck ( I own the Search domain for Magento / Product Management; Any suggestions/ideas to improve please feel free to ping me directly )
Why does search work so well on the backend but terrible on the frontend? I don't get it?
Does enterprise suffer from such capabilities? no.. neither does prestashop, shopkart, woocommerce, bvcommerce, bigcommerce, shopify or volusion... ok, some better than other true but magento's inability to fetch even something similar to the users search, one must get strategic in creating products.
I could talk all day about functionality and capabilities, I think if we just get the better results would be the key. Lets get that right and then an addon's that posses the reporting and weighted results could be an awesome extension I would think.
Ok i was a bit harsh, I apologize..To explain, I've been with Magento since it's infancy and this has been my arch nemesis in more way's then I care to explain.
@choukalos IMO the top priority (apart from making the default search return reasonable results, which is kind of obvious) should be making both the search process (e.g. weighting of product attributes, filtering out certain products) and the search result page (visual representation, e.g. grouping results by product type/category/etc) as easy to customize as possible. There is no one-size-fits-all solution, so ideally developers should be able to customize Magento's search module without having to rewrite it completely.
+1 for making this a top priority and for a more customisable and extensible search module.
@Landkeks - in our upcoming December ( platform beta ) release we'll introduce search modularity to Magento 2 that should address the communities desire to customize all aspects of search (which I've gotten lots of feedback on this need).
Unfortunately I haven't gotten as much feedback on technical suggestions to fix the search algorithm ( mysql/default out of the box). Lots of suggestions on configurations/merchandizing features. Are there any agreed upon technical suggestions on how to improve search accuracy? I have a few but not necessarily correlate. We'd appreciate any suggestions you or the community have to improve the algorithm.
@choukalos From a technical view,
Also less technical, more functional requests:
Just another suggestion - the way how synonyms work:
Right now, when I add a synonym for a search term, magento finds only results, when the customer searches exactly for the term I set an synonymy up. It would be much more useful if every occurrence of that word would be replaced even in search terms with additional words.
This would obviously need more work from the shop administrator but would definitely lead to better results, as you could use it to smooth out common spelling mistakes as well.
+1 for global word-based synonyms, AND matching, and stopwords.
@barbazul Thanks for the insights! Stopwords I believe require a mysql compile to change or a SOLR config not sure we can wrap a Gui around that - I'll check with our architects.
@barbazul - thanks for the insights on the PHPDig library ( http://www.phpdig.net/navigation.php?action=demo ); looks like the code hasn't been updated since late 2005. I'll ask our search architect to look into it and how we might further change our search indexer/search algorithm to be more accurate.
I have built an ElasticSearch indexer for a client site; It works amazing and I am currently creating the module (learning how to build Magento modules); but I am very experienced with ElasticSearch in general.
We would be very interested to hear how successful you are swapping out the default search engine. Have we go the APIs right to make it easy to drop in a different engine? Feedback and suggested changes appreciated. (We don't have much documentation done where the interfaces are, and this is relatively low priority to other documentation. If you are unsure from looking at code, feel free to ask questions.)