Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
nylyon Posted February 7, 2012 Posted February 7, 2012 My forum is about tractors which have model numbers like C-160, B-80, C-195 etc... Search doesn't like to search with the dash (hyphen). When I turn off FULLTEXT native search, I can search with the hyphen but it's slow and inaccurate with other searches. I loaded up Sphinx in hopes to get a great search but I am at a complete loss how to configure it so it will search for items like mentioned above. Can anyone help me so I can get search working for my data? I am using the standard IPB configuration generated file for the Sphinx configuration.
nylyon Posted February 7, 2012 Author Posted February 7, 2012 I wish that I knew PHP, it seems to me that the the Hyphen is getting stripped out and never even passed to Sphinx. Anyone know where the search routine is located, maybe I could dig through it and see if that may be the case. I say this because if I stop the searchd daemon, then run a search for C-160, IPB comes back and says that C160 is not found. If the damon is stopped, could Sphinx even have stripped it? Also, it doesn't seem that the Sphinx escape character is doing anthing (or the wildcard "*" character)
nylyon Posted February 7, 2012 Author Posted February 7, 2012 I found the module: /admin/applications/core/modules_public/search/search.php which seems to be replacing several characters $_search_term = trim( preg_replace( '#(^|s)(+|-|||~)#', " ", $search_term ) ); Is this on the right track?
nylyon Posted February 17, 2012 Author Posted February 17, 2012 Ok, I found the problem and it's not Sphinx. See this post which shows where the problem is, and an enhancement request to make it right. Worst case scenario, you have to modify the core IPB code, BUT be sure that you have the proper char_table set in the conf file. My testing worked but I am apprehensive in applying it until someone from IPB can look and see to be sure that I don't break anything else.
Management Matt Posted February 27, 2012 Management Posted February 27, 2012 This has been fixed in 3.3.0.
Markus Lassfolk Posted February 27, 2012 Posted February 27, 2012 We have also experienced problems doing search with Swedish extended characters åäö ÅÄÖ. We suspect it's the highlight function that got problems with some browsers (IE on one of my computers, but not any problem with FF). Anyone experienced any similar issues?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.