I am using uskinned theme and i have problem with search box.
If i enter this text in search box " Select * " (it can be any word with special character and space between, or 2 letters with 2 spaces betweeen) I am getting this error "Supplied string is null or empty" on this line of razor view:
var terms = searchTerm.Split(' ').Select(x => x.MultipleCharacterWildcard()).ToArray();
This is part of code where things going wrong:
if (searchTerm.Contains(" "))
{
var terms = searchTerm.Split(' ').Select(x => x.MultipleCharacterWildcard()).ToArray();
//Search limited to 4 terms: ref maxClauseCount is set to 1024
if (terms.Length > 4)
{
searchError = true;
}
else
{
examineQuery.And().GroupedOr(new List<string> { "contents" }, terms);
}
}
else
{
examineQuery.And().GroupedOr(new List<string> { "contents" }, searchTerm.MultipleCharacterWildcard());
}
I think its problem with .Split(' ') but i dont know hot to fix it.
I usually do some pre-filtering of search terms to make sure the standard words that cause issues are excluded (double spaces, the word 'and' etc) in this instance perhaps you need to remove the asterisk as maybe it's making all terms wildcarded?
It would be worth dropping uSkinned a line to see if is something with this code that they're aware of.
The other place to check would be how the analyser is setup in examineIndex.config and examineSettings.config.
I have found solution, problem was little above in this part of the code:var regex = new System.Text.RegularExpressions.Regex(@"[^\w\s-]");
I replaced @"[^\w\s-]" with "[^a-z0-9]" and now it works great.
Been playing about with this and the problem is that the * adds an extra space, which then is used in the split giving a null reference.
I think this may be better:
var regex1 = new System.Text.RegularExpressions.Regex(@"[^\w\s-]");
var regex2 = new System.Text.RegularExpressions.Regex(@"[ ]{2,}");
searchTerm = regex1.Replace(originalSearchTerm, "").Trim();
searchTerm = regex2.Replace(searchTerm, " ");
The first regex removes unsafe characters.
The second regex removes multiple spaces.
I am no expert on examine and regex however what we are trying to do is make the search query safe.
Maybe someone else in the community has experience in this and can confirm if this code is okay.
search box error on uskinned theme
I am using uskinned theme and i have problem with search box.
If i enter this text in search box " Select * " (it can be any word with special character and space between, or 2 letters with 2 spaces betweeen) I am getting this error "Supplied string is null or empty" on this line of razor view:
This is part of code where things going wrong:
I think its problem with .Split(' ') but i dont know hot to fix it.
Hi Josip,
I usually do some pre-filtering of search terms to make sure the standard words that cause issues are excluded (double spaces, the word 'and' etc) in this instance perhaps you need to remove the asterisk as maybe it's making all terms wildcarded?
It would be worth dropping uSkinned a line to see if is something with this code that they're aware of.
The other place to check would be how the analyser is setup in examineIndex.config and examineSettings.config.
Good luck,
David
I have found solution, problem was little above in this part of the code:
var regex = new System.Text.RegularExpressions.Regex(@"[^\w\s-]");I replaced @"[^\w\s-]" with "[^a-z0-9]" and now it works great.Hi David,
Thanks for reply. I will try to make some pre-filtering like you said. I have allredy contacted uskinned yesterday but no reply yet and need it fast.
Hi Josip,
Marc from uSkinned here. Can you confirm if the following change to the code solved your issue?
@"[^\w\s-]" with "[^a-z0-9]"
Kind regards,
Marc
Hi Josip,
Been playing about with this and the problem is that the * adds an extra space, which then is used in the split giving a null reference.
I think this may be better:
The first regex removes unsafe characters. The second regex removes multiple spaces.
I am no expert on examine and regex however what we are trying to do is make the search query safe.
Maybe someone else in the community has experience in this and can confirm if this code is okay.
Cheers,
Marc
Hello Marc,
Thanks for reply.
I have tried your solution and its better than mine, because my solution somehow skip loop for checking number of words which is limited on 4 words.
BR
Josip
is working on a reply...