Thank you Sophivorus for opening this case. I wonder why the behavior has changed in MW 1.31.
We have this problem in all our MW 1.31 installations.

I think this is a good idea! Are you able to change this @Samwilson?

I did not notice this problem in the recent versions anymore. I think we can close this now!

Yes, great job @Dan.mulholland. Thank you also from my side!

Thank you, I can wait.... ;-)
So I will change

You are the best. Thank you a lot!!!
To clarify, can I use:

$wgCirrusSearchPhraseSuggestUseText = true;

Any news on this option being fixed: $wgCirrusSearchPhraseSuggestUseText

We are looking into it... thank you for the info...
Currently we use MW 1.28.1 and php7.0 ourself and so far with no problems.

Thank you again!

Thank you @dcausse ! This does work!!!
Can I activate it after initializing CirrusSearch or do I have to keep it disabled for now?

ok, here you go....

ok, will do this tomorrow

so the problem still is the same also with the "master" version of the extension: when I run the suggested command I get this:

This is great, thank you!

After updating the CirrusSearch extension to "master" I now get this, so this looks promising. But still, the download for mw 1.28 should work, shouldn't it?

It even works with mediawiki 1.28.0 so I think you might have an old version or you did not follow the instructions 100%.

Sorry, I have been useing CirrusSearch since the beginning and I forgot to update the Elastica extension (Elastica-REL1_26-2703907). Now the "specialpage:version" is working! Sorry again.

The page Spezial:Spezialseiten shows a black page. Here the apache error log:

ok, I will check.

Yes, now if you download the corresponding version for MediaWiki 1.25 the download is ok and the files work. Great job, thank you!

Yes, everything works with the "master" version. Thank you again fort CirrusSearch, one of the best improvements in the last couple of years on mediawiki!!!

So I now tried the "Master" version of CirrusSearch, and here we go. Now the "special page" "Version" is working again. The extension is still showing up as version 0.2 which could be updated, but at least it is working. Maybe someone can fix the 1.25 version of the download.

I used the corresponding version of CirrusSearch
https://www.mediawiki.org/wiki/Special:ExtensionDistributor?extdist_name=CirrusSearch&extdist_version=REL1_25&extdist_submit=

Sure can do ;-)

No it is not actively a problem, just a nice to have. Thank you

@Manybubbles: I tried running * in the middle and at the end of a word:

And also: I tried the master version of elastica and cirrusserach from today with my current 1.24.1 installations. With those versions the "MW Version" page is totally broken and does not load. Just for your info.

Hello Menybubbles, sorry for getting back to you so late.

The problem seems to be back with the master version of CirrusSearch and Elastica and mw 1.24.1.

I can confirm that this is resolved now. I tried the "master" version of CirrusSearch together with MediaWiki 1.24.1.

Thank you Andre!

Problem still existing in MW 1.24.0

Just a short info with MediaWiki 1.24.0. When I use "php updateSearchIndexConfig.php --reindexAndRemoveOk --indexIdentifier now" as Chad suggested the same PHP Warning pops up. See below.

Ok, got it. Thank you Chad and thank you Manybubbles.
CirrusSearch works great also in 1.24.0 so far, just wanted to report the "error".

OK, thank you for the info Chad. How would you suggest to "reindex"?

Sorry guys, I now know this is not a CirrusSearch problem but a mediawiki "job" problem described here:
https://www.mediawiki.org/wiki/Extension_talk:Replace_Text#MediaWiki_1.22_and_newer_do_not_execute_jobs

Sorry to bring this up again but in the new release of mediawiki 1.24.0 and the up to date version (master) of CirrusSearch one still has to insert this into LocalSettings.php for the jobque to work.

Update: Same with MediaWiki 1.24.0

Ok, I will talk to Felipe. I think it is a great idea and hopefully we will go this way...

Hello Aklappert, yes as we are the maintainers ;-)

Same problem with IE11 (just tested with Windows 8.1)