So changing

Steps to reproduce:

Edit:
Managed to get it working using Elasticsearch 1.7.5 and running

composer require ruflin/elastica "3.*"

after installation of Elastica- and CirrusSearch-Extension.

@Kghbln: Sound's like a good idea. Will do that. Thx

In T137668#2417786, @Kghbln wrote:

@RacingRalf I think it is best not to touch "composer.json" starting with MW 1.25 but rather put everything into "composer.local.json". This apparently defeats regular composer require actions but that's the way it is now.
Then looking at this it think it is also best not to mix tarballs of MW 1.27 and installing stuff via Composer in an extra step.

In T137668#2417760, @mwjames wrote:

Exactly, and before someone is pointing fingers, doing a simple composer update on the plain MW 1.27 tarball just results in:

Found it:

In the vendor folder at the MediaWiki root, do you have a symfony/process folder? Does it show on Special:Version?

Exactly the same problem here. Installed MW 1.27 from tarball. Can't get SyntaxHighlight running.

No clue how common those conditions are.

Any news on this? Tried again with a fresh installation of 1.27 and still can't login. No matter, if I use `$wgSessionInsecureSecrets = true`` and/or `$wgSessionPbkdf2Iterations = 10001;``

Same in 1.27RC0 for Extension:AdminLinks
But without installing ShortUrls

In T136587#2344295, @Tgr wrote:

It sounds like you have set $wgSessionPbkdf2Iterations to 0.

After applying the path and trying to create a new user, I get

If you change line 545 in /includes/SpecialProtectedpages.php from

'ls_field' => 'pr_id', 'ls_value = pr_id'

to

'ls_field' => 'pr_id', 'CAST(ls_value AS INT) = pr_id'

everything's working.