@Ladsgroup Thank you for taking the time. Consider pasting your script in T165538 as a basis for any work that happens there.

This is probably due to MediaWiki\OutputTransform\Stages\ExpandToAbsoluteUrls, which Parsoid uses by default and legacy doesn't -- but that stage just calls Linker::expandLocalLinks which uses wfExpandUrl so there is perhaps something wrong with how MFE is setting up the hostname?

Looks like this is resolved now,
https://en.wikipedia.org/wiki/Device_(Device_album)?useparsoid=0&oldid=850576567#Weekly_charts
https://en.wikipedia.org/wiki/Device_(Device_album)?useparsoid=1&oldid=850576567#Weekly_charts

This seems like a Parsoid problem, and it may be a new issue – otherwise it would have probably come up before, and I don't recall seeing this problem.

Have a look at the Migration to Parsoid read views section of the README of the ParserMigration extension and let me know if that works for you
https://github.com/wikimedia/mediawiki-extensions-ParserMigration

The page exists at https://www.mediawiki.org/wiki/Help:Lint_errors/night-mode-unaware-background-color so we just need to add a redirect. It seems the other lint categories are also redirects from that help link so that probably needs updating as well.

Rather than revert that patch, it could be backported to .22

You'll still need to patch above but it can be rebased on yours and cleaned up. Happy to do that if you want.

I don't think that patch fixes this issue. It does help in that the check ( $parent->getAttribute( 'id' ) !== 'mf-section-0' ) in the patch above can be removed.

https://en.wikipedia.org/api/rest_v1/page/html/0 render the correct page now

Post-deploy to group0 today, MultimediaViewer is opening on officewiki pages. It sometimes requires a purge.

The source is

See if we can preserve git history of Cite development in Parsoid

Examples are from https://en.wikipedia.org/wiki/Help:Introduction_to_images_with_Wiki_Markup/1?useparsoid=1

This smells like PHP seeing "0" and evaluating it as boolean false

Post-deploy, there are instances of this error on 1.42.0-wmf.18