Tweet
Sorry if this has been posted/answered before...
I noticed in our forum that the search wildcard, even though it's enabled in the settings, does not work when it's used in a search term.
Let's suppose that I want to search for "Burgman".
If I give the word itself results come up.
However, if the search term is something "Burg*", "*urgman", "Bur*man" or even "*urgm*" nothing comes back.
Our database has a Greek collation and the languages setting is ISO-8859-7.
Is there some kind of setting I'm missing at the database server level that does not allow for wildcard character usage?
PS
I also tried this here, via this post and I noticed that if I search for example for "Vestibulum" or "Vestib*" the tread is returned in the results. However searching with "*bulum" does not yield any results. I also noted that the term "Vest*lum" brings back irrelevant threads.
I noticed in our forum that the search wildcard, even though it's enabled in the settings, does not work when it's used in a search term.
Let's suppose that I want to search for "Burgman".
If I give the word itself results come up.
However, if the search term is something "Burg*", "*urgman", "Bur*man" or even "*urgm*" nothing comes back.
Our database has a Greek collation and the languages setting is ISO-8859-7.
Is there some kind of setting I'm missing at the database server level that does not allow for wildcard character usage?
PS
I also tried this here, via this post and I noticed that if I search for example for "Vestibulum" or "Vestib*" the tread is returned in the results. However searching with "*bulum" does not yield any results. I also noted that the term "Vest*lum" brings back irrelevant threads.