exc1usive

By search result feedback you mean this string template “Found %d result while searching for %s”?!))) If yes, than yes – so far, I came across this behavior only in the search result feedback.
If more precise, I would say you may see it in the returned by the function $PDb_Combo_Multi_Search->current_search_term() value.

I don’t quite understand your answer. I didn’t say anything about “combo” input, we don’t use this type of search. All fields on the search form are fields with selectors – Multiselect Checkbox, Multiselect Dropdown, and Dropdown List. The only exception is Currency field where a user makes manual input in “from”-“to” fields.
We don’t set any settings on “Combination Search Settings” tab. We provide search fields list in “Multi Search Fields” on “Multi Search Settings” tab. I just tried to set a checkmark for “Whole Word Match Only” setting on “Multi Search Settings” tab, but it didn’t do anything. The search itself works fine, it produces the correct list of participants. The only problem with the translation of “multiple word” search terms in the string

Found 1 result while searching for Electrical fitter, Germany, Austria.

Everywhere else this “multiple word” option gets its translation.
So, this Multiselect Checkbox field has following options defined “General worker, Mechanical fitter, Electrical fitter, Pipe fitter, Welder”. Only “Welder” from this list gets its translation, since it’s a single word option. Once again, we are talking about search term translation only in this string “Found %d result while searching for %s”, everywhere else all options get their translations.

The only workaround I can think of is to set up a “display” value and use only single-word values. In this case everything should work correctly.

General::General worker, Mechanical::Mechanical fitter, Electrical::Electrical fitter, Pipe::Pipe fitter, Welder::Welder

I think this limitation should be included in documentation.

Thank you for your response. It solves the problem from my second question.
What about the first one, when the search form has Multiselect Checkbox options?

The options on the form got translated, but in the text with search terms the filter remain their default values.
Here is an example how it looks on the page. This is English version:

Found 1 result while searching for Electrical fitter, Germany, Austria.

And this is the German version of the same search:

1 Ergebnisse bei der Suche nach Electrical fitter, Deutschland, Österreich gefunden.

The search terms – “Germany, Austria” come from Multiselect Dropdown fields, and they got translated. The search term – “Electrical fitter” comes from Multiselect Checkbox field, and values are always in English (default language).
To translate user-defined strings we use parser in pdb-translate_string filter. As I stated before, it might happened because of leading comma in search terms for Multiselect Checkbox field.

• This reply was modified 6 years, 8 months ago by exc1usive.

Your update fixes the issue.
Thank you!

Yes, indeed! But, I don’t set the values for those search fields during this experiment, they are just left out blank.

I’m using theme’s page template to display the list. It has some logic in php and html markup. Since I put the shortcode in php, I have to use echo do_shortcode(…); function.

But, the issue lies somewhere else. I simplified everything by removing the usage of templates, but the problem is still there.
So, here are the steps to reproduce the problem:

1. I created blank page and placed shortcode [pdb_list template=multisearch] directly to its content. No php, no html, no templates this time.
2. In my functions.php, I removed all unnecessary logic and the loop where i altered the query list object, and just used constants in action, like this:

function filter_by_avalability_dates($query_filter) {
    $query_filter->add_filter('user_login', '=', '2@mail.com', 'OR');
    $query_filter->add_filter('user_login', '=', '1@mail.com', 'OR');
}
add_action('pdb-list_query_object', 'filter_by_avalability_dates');

That is it! Now, on my search form I set filter for only one field, any field, and have this result in my debug log.
(just where portion of the query)

WHERE (p.work_country LIKE "%Austria%" AND p.user_login = "2@mail.com") OR p.user_login = "1@mail.com"

The expected result would be:
WHERE p.work_country LIKE "%Austria%" AND (p.user_login = "2@mail.com" OR p.user_login = "1@mail.com")

See the difference? I don’t know how you might have different result in your tests? I definitely doing something wrong.
If I change OR to AND for the first value (only for an experiment):

function filter_by_avalability_dates($query_filter) {
    $query_filter->add_filter('user_login', '=', '2@mail.com', 'AND');
    $query_filter->add_filter('user_login', '=', '1@mail.com', 'OR');
}
add_action('pdb-list_query_object', 'filter_by_avalability_dates');

The query would be
WHERE (p.work_country LIKE "%Austria%" AND p.user_login = "2@mail.com" AND p.user_login = "1@mail.com")

As you can see, in parenthesis goes only expressions joined using AND. I would like to put parenthesis around ORs.

Roland, I followed you suggestion and enabled debug mode. Here is an example of the query that was generated after applying filter for list view.

PDb_List::_setup_iteration list query: SELECT p.id, p.full_name, p.qualification, p.work_country, p.wage, p.country, p.native_language, p.additional_languages, p.details FROM wp_participants_database p WHERE (p.role = “user” AND p.approved = “yes” AND p.work_country LIKE “%Austria%” AND p.user_login = “2@mail.com”) OR p.user_login = “1@mail.com” ORDER BY p.date_updated DESC

so, this part comes from the shortcode

this part is from filter form

and the last part

was added in action ‘pdb-list_query_object’ I was talking about in previous post.

As you can see first value of custom filter goes in parenthesis with the filter from the form, I was expecting to see something like this:

SELECT p.id, p.full_name, p.qualification, p.work_country, p.wage, p.country, p.native_language, p.additional_languages, p.details FROM wp_participants_database p WHERE p.role = “user” AND p.approved = “yes” AND p.work_country LIKE “%Austria%” AND (p.user_login = “2@mail.com” OR p.user_login = “1@mail.com”) ORDER BY p.date_updated DESC

P.S. “Enable Filter Mode” option is ON, and always was

• This reply was modified 6 years, 8 months ago by exc1usive.
• This reply was modified 6 years, 8 months ago by exc1usive.
• This reply was modified 6 years, 8 months ago by exc1usive.