well, you are right, search is a bit "special": it does not serach for any substring characters that match, but for WHOLE WORDS. the advantage of this is that if you search, forinstance, "road abbey", you'll get the album "abbey road" as a result. the other way, you wouldn't get any result...

in any case, if you really need this character matching criteria, there's always a small code add you can perform to achieve it.

Germi

Hi Germi,

My presumption is that if we search for "abb", we should find it in any string that has it as substring; regardless of it's position in the string and context. For multiple words as search string, I would guess an intersection of searches for individual words would do, of course with an efficient algorithm to do it. And to take it even one notch higher agrep style search would help bad typers like me ) But these could be added search options. I don't have a specific requirement from the client, but I suspected this might come up sometime.

Something interesting I fond out is that it seems to work with unicode chars. I tried a chinese partial search, and it seems that it's able to find the item

awesome!

BTW, is your site in Chinese?
you may want to know that we have a Traditional Chinese language pack on our downloads area! kindly contributed by one of our users

Germi

Thanks for the info. on the language pack; it's great to know that. The site I am working on is based on English. However, it seems that I had two songs in Chinese that I uploaded as well. The title got entered fine in the software and database, but the OS chopped the file name and just put .mp3 (basically no file name). But it works fine on play since .mp3 is a valid file name On the second upload it generated ####_.mp3 (where #### is the random number) as it probably detected a duplicate of .mp3 and tagged the random number to make the distinction. It works fine though.

Actually I think I found a way to enable "partial search". If you go to com_muscol/models and look at search.php. You can modify get_where_clause_keywords function and change the SQL command to:

(al.keywords LIKE '%".$keyword[$i]."%') AND

This basically removes the whitespace requirement before and after the keyword. So if you type "ab" in the search field, it'll return all albums/artists with an "ab" in it. I don't know if this is the behavior you want.