Fixes a few issues about FilterQuery in listconfig,

[Yuanuo]

1, if FilterQuery (such as q) is configured in the Listconfig, it will not be replaced with a real search string if it contains %(query).

2, The new Listconfig is forced to specify Locale as en, and the configuration of en is also read first in hard-coded, and if you want to use a List configuration in a multilingual environment, it always read en's configuration (although there may be other implementation methods, such as creating multiple List configurations). So add a macro "%(locale)" and you can configure it in this way with q={!qf="content_%(locale)"}%(query).

Made such a code change: Yuanuo@9d7513c

[dSeidel]

Hi @Yuanuo , thanks for the suggestion. I added the macros to the master branch (pushed soon) as you suggested. Nevertheless, be very careful using it. There are multiple reasons for this hint:

1. In the integrated list, the query is already modified to use (see CmsSimpleSearchConfigurationParser#getQueryModifier)
2. The field is intentionally called "Filter query" and you should not set "q=" there. It's made for "fq=".
3. The integrated list is a feature to get search up easily with limited configuration. If you want more complex configurations, maybe use your own type or a dynamic function, backed up with cms:search using a json configuration and this configuration can be part of a JSP - meaning you can tweak the configuration as you like without macros.

Moreover, be aware that the "Filter query" options must be url encoded in the current master branch, ie., you have to write the macros url encoded.