Tried to search for a reference, but the words are too short.
The "What's New" button at the top is handy (as is the alternative New Posts link just below it), after a round or two of my preferred old-style meandering through the forums (fora?)
But the message should be changed from "Sorry, there are no new posts to view." to something like "Yesss! You are finally caught up with all of the current events on SF. Nobody has updated one post while you were viewing another one. So take a few minutes off to deal with reality." J/K :cheers: <3
If you search for a short word, i.e. 3 letters, the software returns zero results. This includes acronyms such as "USB", "IBM", "FDA", etc.
If you search for a 2-letter word, the software tells the user that it is too short. So there is a bug counting letters: either excluding 3 letters rather than just 2 letters, or alternatively failing to display the error message for 3-letter words.
This actually isn't a bug in the forum software, but I thank you for bringing it up. It's likely a bug in the admin's ability to configure MySQL appropriately...I'll explain. The forum is configured to allow as small as 3 characters in a search term per the forum settings. This explains why you're not able to search for anything below three characters:
As you might gather from the underlined statement, I've not configured MySQL to index smaller words for searching. I will need to take a look at the configuration for our database and make appropriate changes. Last I remember, the smaller the number of characters, the larger the index becomes and the longer it takes to rebuild. I believe vbulletin by default uses 4 characters. Even though I changed it to 3 in the vbulletin settings, it can't make use of this because there is nothing found in the index...hence why you had no results returned.
I need to make the following changes to the my.cnf file to allow MySQL to index smaller lengths of words:
This is now implemented and fixed. I'm able to search for USB, IMB, etc (not etc literal) and it returns results. The index is finished rebuilding and should be ready to serve your needs for three-character and larger searches.
I don't suppose you have any control over the parser's selection of delimiter characters? No doubt just wishful thinking on my part that fullstops shouldn't be thrown away unless followed by spaces or CRLFs - fullstops are often used as decimal points on an english language technical forum, eg USB 3.0, Catalyst 12.2, etc.
A mini-list of common 2-letter words that should be thrown away (eg. an, in, on, is, it) doesn't sound that hard either, if you happen to feel motivated enough to suggest that to the developers.
It may not look jazzy, but it sure is functional. Additional glitz will just increase loading time. Have no idea where you are located, GabrielMl, but members here are spread all over the world and many are on speed & bandwidth-limited connections.