Document wildcard support in user search

[valadas]

Description of documentation change

Just learned today that wildcards are supported in user search and tought it would be nice to add this information in the documentation.

Existing documentation section (if applicable)

https://dnndocs.com/content/guides/tutorials/securing-your-site/user-accounts/about-user-accounts/index.html

Proposed area for new documentation (if applicable)

A new subpage called "Searching for users" that documents how the search works, IE right now I learned we can use wildcards * that I was not aware of.

Additional context

I am working on a bug with the search and the "show" dropdown in that area so I may add some more info if I have more findings worth documenting.

[sleupold]

This needs to be tested, but the intention was:
while typing (at least 2 characters), DNN performs a type suggest using a left search in the search input and lists the first matching items beneath, from which a user can select an item, if applicable.
If the user hits :Enter:, an exact match is performed, unless the search word ends on :*: (asterisk).
Likewise, the user may perform a search in the string by prefixing the asterisk - though this might be slow on large user base.
Search is currently performed in the following user fields:

• first name
• last name
• display name
• user name
• email address

[valadas]

That looks about right except the type suggest part, it only lists the results. everything else looks right.

[sleupold]

@valadas
what is the benefit of type suggest, if you can't select from the suggestions?

[valadas]

Well, I did not see any type suggest, I only see the results updating as you type... Do we have a different definition of type suggest ?

[sleupold]

sorry, might be my fault. If it is performing a life filter instead of type suggest, there should be an option to terminate the input, e.g. to filter by "Tom" without getting all "Tomas", "Tomasz" etc. entries.

[sleupold]

btw: there was just recently a request to extend the search on specific profile properties (most likely, extend the result to display some of them in the list as well, e.g. the option to display city or phone number in the list, like in DNN 3 to 8.