Don't know if this was already mentioned, but search is not working when searching for more than one word. Instead of searching for the first word AND second word in posts, it is searching for the first word OR second word.

For example, search "maui blue". You get threads with the mention of blue but the word maui is not to be found in the thread. Its making it real diffilcult to find things.

 

Actually, it does. It is just the fact that the word "blue" is so common, you're getting results for simply "blue". It is not narrowing it down to only posts that contain "maui" and "blue", but instead, any post that contains "blue" or "maui".

 

Must be a bad search algorithm then, because it shouldn't matter how common a word is. Both words should be in each thread that search pulls or at least thats how I always remember it being.

I get this post when searching maui blue but maui is not in the thread:
https://www.thirdgen.org/forums/tech...2Bmaui+%2Bblue

Is there at least a way to enable searches such as "+maui +blue" to get both results in every thread? My recent searches have yield 9,999 results with no answers.

Anyone else having this problem?

 

No. My point was that with as common of a word as "blue" is, you are going to get a lot of results for that word, hence, any results for "maui" may be lost in all those results. I stated this because you first indicated that maui was no where to be found. It is there, but with the amount of posts with blue, it is going to make any maui posts harder to find.

I agree that it needs to be worked on. But I cannot do it.

 

"shift light rev limiter schematic" search results = 10000. It seems a thead only needs one of those words to be a hit, is there a way to search for posts/threads containing all search words? the second hit that comes up this morning is about a guy whose horn doesnt work.

thanks

Andy

 

After a small discussion, Jason turned on the boolean searches, which should aid in these searching issues. However, due to the load that search puts on the server due to the size of the database, some search restrictions had to be turned back on.

 

Thanks, thats much better