Exception in Advanced Member Search v1.0.3

Hi pxt-wpforo-2018,

Please update to 1.0.5 version.

Thank you Tom. I have updated to 1.0.5 and I see the specific search in my post above now produces the correct records.

Another search on the same fields does not work as expected. Using the default field Display User and a custom field called Test; in the user profile of Fred, set the Test field to value "Test".

• Search Display Name = "Fred", Test = "Test", returns Fred, OK.
• Search Display Name = "Fred", Test = "Banana",  returns no records, OK.
• Search Display Name = "Banana", Test = "Test", returns Fred
• Search Display Name = "Banana", Test = "Banana", returns no records, OK

When the Display Name is a match, but the custom field is not a match, no records should result.

When the Display Name is a match, but the custom field is not a match, no records should result.

The search condition is OR not AND. We'll consider to add condition changer in future releases.

No end user is ever going to figure out the inconsistencies between default fields and custom fields.

The two default fields work together as an AND. The default and custom fields now work as OR. This can't be right.

Display Name = "Fred", Nickname = "mark" produces no records, as an AND, as users will expect.

Display Name = "Fred", Test = "Banana" produces Fred, as an OR, as users will never figure out. The OR is different from example search forms that users see commonly.

I just checked what happens when there are multiple custom fields on the search form. The custom fields work together as an AND, as users will expect. The default fields work together as an AND, as users will expect.

Please don't be offended, but I am sure it should all be AND, consistently.