View Full Version : Please consider allowing 3char search terms: example: MWF, SOC, 620, XTG
aimsport
08-20-2010, 03:29 PM
Please consider allowing 3 character search terms so that search for SOC with MWF would come up with posts, for example.
Thank you.
AlanL
08-20-2010, 03:33 PM
In the meantime, you can work around this with a google search:
soc mwf site:badgerandblade.com
Or use the google search box installed on B&B in the drop down box-
You can also search it with a star
MWF*
But Google will work better I think...
aimsport
08-21-2010, 12:06 AM
Thank you all for the suggestions.
aimsport
08-23-2010, 03:32 PM
Here's the link on how to do this in VBulletin
https://www.vbulletin.com/docs/html/main/options_search_minchars
It's changing ft_min_word_len to this:
[mysqld]
ft_min_word_len=3
[myisamchk]
ft_min_word_len=3
And rebuilding the index.
Then VDH, SCS, RAD, SOC, QED,... etc... would be searchable.
aimsport
11-13-2011, 05:30 AM
Any hope that three letter searches would be supported soon?
Here's the link on how to do this in VBulletin
https://www.vbulletin.com/docs/html/main/options_search_minchars
It's changing ft_min_word_len to this:
[mysqld]
ft_min_word_len=3
[myisamchk]
ft_min_word_len=3
And rebuilding the index.
Then VDH, SCS, RAD, SOC, QED,... etc... would be searchable.
SpecialK
11-13-2011, 07:42 AM
It will be possible in the future, but no timeline. We will be moving away from mysql's fulltext search engine (it's awful) and when we make that move, 3 character search terms will be enabled.
Viseguy
11-16-2011, 07:03 PM
... We will be moving away from mysql's fulltext search engine (it's awful) ...
Good news!
ulbador
11-23-2011, 09:33 PM
It will be possible in the future, but no timeline. We will be moving away from mysql's fulltext search engine (it's awful) and when we make that move, 3 character search terms will be enabled.
I actually just made this move myself on my corporate website. That full text search was KILLING our database farm no matter how we optimized or or handled things. Ultimately, our solution was running a Sphinx daemon.
I'm pretty sure the later versions of VBulletin implement Sphinx. Though because our codebase is all custom I went full-on and compiled Sphinx directly into the MySQL daemon. Amazing difference!
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.