dont know if I totally understand what you mean...

the first three are for albums. the same albums, but showing different views. usually, you pick up the same you use for artists (detailed , in my case)

Hi Germi,

There doesn’t seem to be any difference in the format for all three, they all showing detail for albums. Currently I have the menu item type set to search:

option=com_muscol&view=search

When we go to the page it has the search bar, search form, and automatically searches for all albums. Now I have couple of more questions.

1) Can we turn off the auto search as we go to the page and just show
the form and no results
2) Can we set the search to be for something else than the albums
3) Is there a search form module that I can use instead? How did you
do your demo?

Thanks much in advance.

1) well you'll need some code for that... :S that was precisely changed on version 2 because most of the people didnt like it to show a page with no results... :S

2)... like what? only two searches are possible: albums or songs. what you want to search?

3) yes there's a search module for version 2:http://www.joomlamusicsolutions.com/downloads/doc_details/55-search-bars-module-for-music-collection-2.html?lang=en
(but we are not using it on our site!

Thanks Germi,

I was thinking about partial searches like albums that start with some specific string or artists that their names start with some specific string or character. But you are right, it's probably better to just display all the list since it's paged and only a small set is display at one time. But we seem to not be able to do a partial search by putting for example C* in the search input form and get all albums that start with C. Unless we need to do something specific?

Thanks for link to the module. You are right, I probably don't need it, but I play with it if I get a chance.

Thanks again.

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.

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.

that's right. that's the way to do it

Thank you very much gomakeit. I'll test around it.