Thanks!

In T8920#181662, @Stefahn wrote:

Thanks for looking into this. It's a pity that there is no easy solution.
But I second Reception123. The ability to sort by PageUsage should be removed alltogether then. Who can do this?

Thanks for looking into this. It's a pity that there is no easy solution.
But I second Reception123. The ability to sort by PageUsage should be removed alltogether then. Who can do this?

In T8920#181532, @Universal_Omega wrote:

Apologies, but unfortunately we can't really easy make this change for usage of this, per above. Therefore I'm going to go ahead and close this task as declined. I apologise for the inconvenience.

Apologies, but unfortunately we can't really easy make this change for usage of this, per above. Therefore I'm going to go ahead and close this task as declined. I apologise for the inconvenience.

In T8920#181520, @Universal_Omega wrote:

As far as I'm aware this has no solution due to limitations with the MediaWiki pager system, that can only be used for sorting by database values, not formatted output.

I think this is caused by the fact that the database table, rl_pageusage is a list of pages it's used on, when using sort it sorts alphabetically for that value, not by the formatted count displayed on the table. As far as I'm aware this has no solution due to limitations with the MediaWiki pager system, that can only be used for sorting by database values, not formatted output.

@John Is there perhaps some easy fix to this? I wonder if it's just one of those things where there's a typo or very minor issue with the code.

I can confirm this can be reproduced on Miraheze wikis.

https://github.com/miraheze/RottenLinks/pull/41

• T7942: [ManageWiki] Create better CI for MediaWiki standards and security
• T7943: [CreateWiki] Create better CI for MediaWiki standards and security
• T7944: [MatomoAnalytics] Create better CI for MediaWiki standards and security
• T7945: [GlobalNewFiles] Create better CI for MediaWiki standards and security
• T7946: [RemovePII] Create better CI for MediaWiki standards and security
• T7947: [DataDump] Create better CI for MediaWiki standards and security
• T7948: [RottenLinks] Create better CI for MediaWiki standards and security
• T7949: [IncidentReporting] Create better CI for MediaWiki standards and security
• T7950: [WikiDiscover] Create better CI for MediaWiki standards and security

In T7939#160072, @John wrote:

In T7939#160067, @RhinosF1 wrote:

In T7939#160062, @John wrote:

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

It's one end objective that all Miraheze maintained extensions have mediawiki-standard CI

9 different software components = 9 different tasks surely? They just good task management and makes things easily trackable and measurable.

It's probably better to be tracking things separately and have subtasks for each extension

In T7939#160067, @RhinosF1 wrote:

In T7939#160062, @John wrote:

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

It's one end objective that all Miraheze maintained extensions have mediawiki-standard CI

In T7939#160062, @John wrote:

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

It's one end objective that all Miraheze maintained extensions have mediawiki-standard CI

One task - one end objective is a standard purpose. Why do we have a task for 9 separate objectives?

I've extended the above mentioned PR to now also include phan.

https://github.com/miraheze/ManageWiki/pull/297 does this for ManageWiki, implementing eslint, stylelint, and phpcs. It also will make GitHub Actions automatically commit formatting fixes, when possible.

It has now been deployed. So yeah there was just a couple logic fixes to it that prevented the actual HTTP: <code> from appearing.

Indeed, much nicer!

Great! Once deployed I recommend updating the extension as well as it includes a couple of additional fixes to the actual special page as well.