All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Is there a known issue with searching grid item when the language is not in latin characters such as Hebrew, Sansikrit or Arabic ?

Merv 16 Apr 2014 12:09 question, complete

Replies

  1. Low 16 Apr 2014 12:39

    Not that I know of.

  2. Merv 16 Apr 2014 12:49

    OK thanks. Search works with input text fields alright. But when searching grid items, it does not seem to be reading any values of those items when the language has characters different from latin.

    thanks anyway for your prompt help, I will try to find out.

    Merv

  3. Low 16 Apr 2014 12:52

    Check how it's actually stored in the DB. Could be EE uses entities to store the other characters. That might screw up matching.

  4. Merv 16 Apr 2014 12:53

    Hi sorry about my badly written reply. Let me re-phrase....

    If the values in non-latin language are in text input fields, low search has been successful at picking up the values in those fields and retrieving the search result. But when the search targets grid items that have the non-latin language values, low search does not seem to read those values and the returned result does not recognise the criteria based on which the search was made.

    Merv

  5. Low 16 Apr 2014 12:55

    Are you saying keywords="foo" does work, but search:grid_field:column="foo" does not? (where foo is non-latin chars)

  6. Merv 16 Apr 2014 12:58

    Your interpretation is correct (except the search is not by keyword, but rather with dropdown lists with pre-defined values).

  7. Low 16 Apr 2014 13:02

    Can you share your Form code (You can use http://pastie.org/ or http://pastebin.com/ for large chunks of code)

    Also, what's the URI for a search that does work, and one that does not?

    For the search that doesn't work, check the Output Profiler and look up the query that targets a Grid table (looks something like exp_channel_grid_field_xx); what does that query say?

  8. Merv 16 Apr 2014 13:12

    Hi, I have to apologise as I tried this in a different template and the search worked. Let me spend time checking that template to see where the problem lies, I might well resolve it myself.

    Thank you

    Merv

  9. Merv 16 Apr 2014 13:59

    Hi

    It was a syntax error in the template code. Sorry for the inconvenience.

    Thank you