I think you are referring to Lucene (https://en.wikipedia.org/wiki/Elasticsearch references it being a Java frontend for Lucene, but on a PHP system you'd typically not have Java servlets installed).

There are other issue(s) on the tracker for discussion of integration of other search systems, but it would be a multi-week project at least.

I guess, i am not a programmer, i just know on our current site that is just apache, mysql and php, tikiwiki is able to choose mysql, Lucene or Elasticsearch.

the later returning search results the way more people would expect, compo.sr does not return results on any way that makes sense to me or our users. if its to hard that is fine, i will stop looking at compo.sr as our new site software.

We have issue #1479 for implementing Sphinx, which is similar to Lucene / Elasticsearch.

And we have issue #3288 for improving our own search engine as an alternative.

We'd be talking about getting funding of somewhere between $2000 to $4000 to implement, so we'd need an organisation to sponsor this.

Or, you could try and place a very specific feature request saying the results you got, the results you expected, why you expected those results, and what exact content entries would need to be added to a clean Composr CMS install to replicate the problem. Then we might know a specific issue to look at in more detail.

You originally made the report for compo.sr (our website for Composr CMS), not Composr CMS itself, and you mentioned compo.sr again in your reply. As you are talking about your own website, I assume you are actually talking about Composr CMS itself.

I see you're posting as a guest user, meaning you'll get no reply notification. Hopefully you manually check and see I have replied. Otherwise I'm talking into thin air.