Search is broken with any character that is url encoded, including spaces.
This is easy to test and confirm by turning off next template packs.
For example, a search for the user "Jonathan Moore":
turn off Next Template packs, search returns result (assuming you have the named user) and with "Jonathan Moore" visible in the search box
with Next Template packs, no members are found, and on screen refresh the search box has changed to "Jonathan+Moore" and there is no user of that name.
We can put the url generated by Next Template Packs
/members/?members_search=Jonathan+Moore&dir_members_search_submit=
back into the legacy and again it works fine, the legacy understands that "Jonathan+Moore" should be decode to "Jonathan Moore" for the search.
This applies to other characters in the URL for example:
/members/?members_search=superman%2Fwoman
will correctly search users for the string "superman/woman", but the Next Template Packs will not.
Search is broken with any character that is url encoded, including spaces. This is easy to test and confirm by turning off next template packs.
For example, a search for the user "Jonathan Moore":
We can put the url generated by Next Template Packs /members/?members_search=Jonathan+Moore&dir_members_search_submit= back into the legacy and again it works fine, the legacy understands that "Jonathan+Moore" should be decode to "Jonathan Moore" for the search.
This applies to other characters in the URL for example: /members/?members_search=superman%2Fwoman will correctly search users for the string "superman/woman", but the Next Template Packs will not.