Covering OroCommerce, OroCRM, OroPlatform topics, including community updates and company announcements.

Forums Forums Oro Community Disconsider accentuation on Oro search

This topic contains 3 replies, has 3 voices, and was last updated by  am”>ine.behwan 4 years, 1 month ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
  • #37740

    William Radi

    Hi Oro team!

    Currently, Oro search brings to me (in whole system) different results if I look for “João” and “Joao”.

    How to change it and make Oro disconsider accentuation on search, datagrid, form fields (<select> tag), reports (inside SQL query executed by report)?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Author
  • #37745

    Yevhen Shyshkin

    Hello, William.

    Oro applications work with UTF8 charset which means that “a” and “ã” are different characters. To make it work like you want you have to change every place where it does not work the way you like.

    If you’re using Enterprise Edition and Elasticsearch then you may change default analyzer configuration and add there asciifolding or icu_folding filters. It will cover global search and most of the autocompletes (select form fields).

    As for the datagrid and report filters – here you have to work directly with DB filtering. DB filters are encapsulated at filter classes – e.g. StringFilter. You can override / decorate some of such filters and wrap your column and input into one of the string convert functions which will convert UTF8 e.g. to ASCII. There are two issues here – you’ll need to write (or find) Doctrine function for your conversion, and filters most probably will not use DB indexes so such filtering will be slower.


    William Radi


    Ok… Thanks, Yevhen! :D




Viewing 3 replies - 1 through 3 (of 3 total)

The forum ‘Oro Community’ is closed to new topics and replies.

Back to top