[03:13:09] [discord] Is anyone familiar with Linter setup? I see it's installed, enabled and working on meta for example (so working in MW 1.38) though in betaheze or on other (third party) wikis the `Special:LintErrors` page always shows zeroes. In my own 1.39.1 install, it shows all zeros (despite obvious outdated html tags it should flag). [03:13:52] [discord] The extension page is lacking documentation [03:16:33] [discord] I tried over at MediaWiki discord, and folks there think it should work, but it doesn't in 1.39.1. I ran update.php, it shows in Special:Version, there's nothing in the debug logs, job queue is empty, I've run rebuildall.php in case it's a category link issue. Linting is enabled in parsoid config per linter extension page: [03:16:34] [discord] ```$wgParsoidSettings = [ [03:16:35] [discord] 'linting' => true [03:16:36] [discord] ];``` [03:16:37] [discord] Editing and saving a page in VE, that has obsolete tags, also still does not cause it to show up in Special:LintErrors or any of its subpages. [03:19:31] [discord] I'm trying to determine if it doesn't work for third-party wikis (since it is running and shows results on Meta, I think this perhaps isn't the case, but maybe some (undocumented) modifications or hoops were jumped through to get it running? Like, perhaps in its current state it *requires* a separate parsoid setup/config? [06:06:00] [discord] Nm, looking through the MH mw-config, I see that parsoid needs to be loaded as an extension and parsoid and restbase need to be manually configured... tried that, have already been down that road with MW 1.35, and ran into several of these same issues (the errors that I'm getting now match this): https://phabricator.wikimedia.org/T263928 So... I just don't need Linter that bad lol. Maybe in a year they'll get [06:06:02] [url] ⚓ T263928 VisualEditor in 1.35 not working (404 / Permanent Loading) | phabricator.wikimedia.org