Just realized the example gave was of specific scoped encyclopedia. Is still good example.

I think part of the issue is that I remember it used to be this way originally and is also where some others are coming from.

See proposal in related https://phabricator.wikimedia.org/T24586. This is for using SortKey as rendered link name. But this could just as easily be swapped with DISPLAYTITLE, if that's available in the same DB row. Haven't checked.

What the fix could be, with 1.39 as example:
https://stackoverflow.com/a/77297799/714557

I was just letting you know. Thanks for your attention in this.

In T266419#6903335, @Reedy wrote:

Of course, 1.33 is EOL and has been since June 2020, so we wouldn't reccommend running that either ;).

In T266419#6903327, @Celess22 wrote:

I'm sure this may not make any real difference for the WM environments.

But in a perfect world would be nice if could get pushed into 34 now for the masses, since many will be stuck when they get cPanel upgrades, like dominos falling.

Keep in mind also, that a huge number of people on 1.35 and below are about to have no choice for composer 2.0, and its was presumably easier for you if I come to you with direct feedback on the version you are on yourself. Which is part of the impetus for coming when I did and how I did to let you know.

Thought you may want feedback, since the bulk of what you will get feedback on is only for WM.

Its a parallel POC for a project that's live on ~1.33. Code, servers, custom work all being validated as one would normally want and some expect. :) Not a lot of new unmanaged edits so its easy to revert, roll in or out of any version.

I'm sure this may not make any real difference for the WM environments.

I added your changes for that one file after the clone, which I did before I tried composer, which I did on a fresh clone of 1.36.0-wmf.34.

In T266419#6903227, @Reedy wrote:

In T266419#6903217, @Celess22 wrote:

With 2.0:
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.

That's part of the PHPUnit dependancy tree. Or more specifically, it's a dependancy of phpunit/php-code-coverage (which phpunit/phpunit itself depends on).

It's irrelevant for this bug, and you probably don't want dev packages installed in production anyway.

It'll be fixed/sorted as part of the PHPUnit 9 upgrade; see T243600: Migrate MediaWiki core (and thus extensions and skins) to PHPUnit 9 for the most relevant task

For whatever its worth 1.36.0-wmf.34 was able to fire up, with adjustments, on cPanel version 94.0 build 2 (~2021-03-01). See https://docs.cpanel.net/changelogs/94-change-log/

With 2.0:
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.

On a fixed environment (HWM) that was recently updated to composer 2.0.6 (2020-11-07), I needed to perform this maneuver with 1.36.0-wmf.34 this morning.

cd mediawiki-1.36.0-wmf.34