Search term containing "&" doesn't yield result, Fixed?

It’s still in beta, I’ve been extremely busy, not had time to finalize it and release it.

Alright I understand. Can I join the beta testing and get my hands on it? I will also help you out testing it if that’s what you are looking for.

Let me know.

Yeah, that would be very helpful. Check out this page, it explains how to set up the beta test: https://xnau.com/participants-database-beta-test/

Well I am using the beta version right now. I am using the same way I used the 1.5 version before, haven’t found any problem yet, still testing it, but I can’t get to see records with “&” or any other records for that matter which have a symbol like ampersand or hyphen.

I tried doing the other way round, meaning create the record itself with & instead of just &so when I search in the frontend with & it will be output as html & and it would match the record. But saving the record it doesn’t save it as html, it saves just as &

Any suggestions?

The way it works in the beta version is record data is stored unencoded, and searches are performed using unencoded strings as well…so the & is always just a &…unless it’s rich text.

I have tested the search functions with special characters like &, it works. * won’t work because it’s used as a wildcard in searches.

I think there is a bit of confusion since whatever I wrote in HTML format is rendered in the output form, I wrote & amp ; but it is showing as & here.

Let me rewrite it:
I tried doing the other way round, meaning create the record itself with & amp; instead of just & so when I search in the frontend with & it will output as html & amp; and it would match the record. Only downside is when the record is displayed, it will be displayed with & amp;. But when saving the record it doesn’t save it as html, it saves just as &.

And I didn’t understand what you said, probably even you can use a space in between like this: & amp; to differentiate between html code and the ampersand itself.

And let me know how do I reproduce and make it work.

In version 1.6, HTML entities such as & amp; will be saved as unencoded characters. This means that when someone searches for a record, they don’t have to use an encoded character, they just use the character.

So, to make it work for you, don’t save your records with encoded characters, just save the ‘&’ as ‘&’ then the search for ‘&’ will match those records. It’s much simpler.