PDA

View Full Version : Vbulletin 4.0.1 Search not work with .com


InvestDad.com
01-29-2010, 07:25 AM
Hello buddies,
I just installed vbulletin 4.0.1 here from database of vbulletin 3.8.3
http://www.investdad.com/forum/forum.php
I got SEARCH function not work properly.
When I enter any search keyword like "investdad.com" then no search result found
But "investdad" it generates many results.
Any keyword including "." doesn't work.
I tried to run REBUILD SEARCH INDEX but no luck.
Pls help me asap.
Thanks

Lynne
01-29-2010, 02:11 PM
You need to run rebuild search index and make sure if fully populates the new search tables. This should not just take a minute or two, it should take a while. Did it take several minutes for you? If not, look in your error_logs and see what happened.

Videx
01-29-2010, 11:04 PM
Confirmed here too. May be some sort of odd search thing because if I replace the . with a * (wildcard asterisk) it seems to work.

InvestDad.com
01-30-2010, 08:53 PM
Yes it did take me several mins to rebuild search index. Any search keyword can procedure results but not with "." character within. Lol....

Lynne
01-30-2010, 10:25 PM
Very interesting. Can you guys make sure this is in the bug tracker or it won't get fixed. Thank you.

Videx
01-30-2010, 11:35 PM
Done http://www.vbulletin.com/forum/project.php?issueid=35808 . Investdad, you should mark that you can reproduce the bug.

InvestDad.com
02-01-2010, 11:39 AM
Done http://www.vbulletin.com/forum/project.php?issueid=35808 . Investdad, you should mark that you can reproduce the bug.

Thank for notifying Vbulletin team. Hope they would come out with good solution soon

InvestDad.com
03-09-2010, 10:29 PM
Hello guys,
Is there any futher update due to this search problem? I am still using vbulletin 4.0.1 then should I upgrade to newer version to get this fixed?
Thanks

Videx
03-09-2010, 11:25 PM
Ha. Since you were the one that came up with it, you should be telling us if it was fixed. Of course you should update to 402pl1 ASAP since it fixed so many other bugs, but I really don't know if this one was fixed.