Thread

Hi,
I am having trouble with the search inside EE 1.6.8. One example is the title field. I have an entry with the title “Íslandsklukkan 1943”.

If I search for “Íslandsklukkan” I get result but if I search for “íslandsklukkan” I get nothing. I can of course search for a part of the word like “klukkan” and get results. There seems to be something going on with foreign characters.

I have attached screenshots to clarify what I’m doing.

Any ideas on this?

regards,
Gylfi

Is that only for searching in the Control Panel, or for regular searches as well? It’s probably a collation issue. Do you know which encoding and collation yor db is using?

Also, what version and build of EE are you using?

Hi,
I am using EE 1.6.8 Build: 20090723

MySql charset is UTF-8 Unicode (utf8)
MySQL connection collation: utf8_unicode_ci

forgot to say that this problem is both on regular searches on the website and the Control Panel.

Is “islandsklukkan” used anywhere else? It may just have to do with how the url_title is being generated.

The are 8 entries with the word “Íslandsklukkan” in it. None of them has the same url_title. There are always other words also in the title. E.g. islandsklukkan_1943

gylfisteinn,

Can I get you to update to the latest version (1.7) please and confirm if issue still exists.
Can you also post the search tags from your templates so we can test locally.

I know that the cp search is more limiting when searching via a title so lets test the front end first

Hi John,
ok I’ll try upgrading.

Here is the search form code:

{exp:search:simple_form weblog="pages|news" no_result_page="is/ekkert_fannst" result_page="is/nidurstodur" search_in="entries" show_expired="yes" where="all" limit="1000"}
                    <input type="text" name="keywords" id="keywords" value="" />

                    <input type="submit" class="leita" value='{exp:multi_language:phrase index="search"}'>
                    <input type='hidden' name='sort_order' value='asc' />
                    <input type='hidden' name='langu' value='{segment_1}' />
                    {/exp:search:simple_form}

Gylfi Steinn

Please let us know how it goes. I’ll try to reproduce your issue locally as well.