[00:55:59] <felixphew>	 hi! I've been hitting an error consistently trying to open the visual editor after upgrading to 1.37.x - tracked it down to this exception: Error: Class "Wikimedia\Parsoid\DOM\Document" not found
[00:56:00] <felixphew>	 https://dpaste.org/BinvY
[00:57:29] <felixphew>	 any ideas? as far as I can tell that class should be provided by dodo or DOM/Compat, both of which are... there?
[01:15:27] <TimStarling>	 probably DomImpl.php doesn't get run for some reason
[01:15:44] <TimStarling>	 I simplified this in 802d1bb3ac20135d1ba15bec4026b0a77feacf50 but you're probably using a version from before that
[01:16:23] <felixphew>	 I sure am - funnily enough I'm looking at that commit right now, but it didn't make it into the 1.37 branch seemingly
[01:17:06] <TimStarling>	 it's supposed to be run when the composer autoloader is registered
[01:18:22] <felixphew>	 it gets called in extension/src/RegistrationHookHandler.php, seemingly
[01:19:26] <felixphew>	 if it's not called already
[01:37:01] <felixphew>	 hmm! ok, it's _not_ getting run (or at least, a wfDebug I put at the top is never getting printed)
[01:37:05] <felixphew>	 ok, why
[01:41:46] <felixphew>	 the onRegistration handler for Parsoid isn't getting run - maybe that's expected if it's VisualEditor starting up Parsoid itself, though?
[01:43:52] <felixphew>	 it _does_ get run if I wfLoadExtension Parsoid manually
[01:44:31] <felixphew>	 oh great, now I get Exception: Serialization of 'Wikimedia\Parsoid\DOM\Compat\Element' is not allowed
[01:51:43] <felixphew>	 https://dpaste.org/K9kg2
[01:55:45] <felixphew>	 so DOM\Compat\Element is just a PHP DOMElement, right?
[02:14:32] <felixphew>	 ah! found it
[02:15:06] <felixphew>	 this is hitting T307982, fixed in e199b22
[02:15:07] <stashbot>	 T307982: Visual editor exception with PHP 8.1 on pages that use templates - https://phabricator.wikimedia.org/T307982
[02:18:36] <felixphew>	 so parsoid just needs upgrading to 0.14.1
[02:23:33] <felixphew>	 ah, but composer.lock for 1.37.2 specifies 0.14.0... might need to ask distribution maintainers to patch
[02:35:28] <felixphew>	 or wait for 1.37.3 ig
[03:50:56] <TimStarling>	 ask Reedy
[11:39:47] <Reedy>	 felixphew: 1.37.3 is due out this week
[11:44:54] <felixphew>	 Reedy: ah, excellent, thanks
[14:12:09] <ArrakeenMiner>	 I'm trying to simplify my MediaWiki farm into one file from a GSS with several LocalSettings.php files and was wondering if anyone can help with an issue I'm having. After doing so, one wiki, "wiki1" loads, but the others don't load and I get a central auth error saying:
[14:12:10] <ArrakeenMiner>	 https://pastebin.com/CA9sZpdW is the LocalSettings file, I'm wondering if anyone can point out where I'm making a mistake?
[14:12:24] <ArrakeenMiner>	 the error didn't paste, but its /wiki/wikisitename Error: Call to a member function getCanonicalServer() on null
[14:16:29] <Reedy>	 Is there a line number?
[14:18:21] <ArrakeenMiner>	 Reedy https://ibb.co/NLcMbYL
[14:18:45] <ArrakeenMiner>	 is the error, no line number for the LocalSettings.php file, but it seems to be CentralAuth throwing the issue?
[14:19:18] <Reedy>	 Yeah, but with "Error: Call to a member function getCanonicalServer() on null" alone we can't tell you what's wrong or where :P
[14:20:21] <ArrakeenMiner>	 doesn't seem to be giving me any more than the error in the screencap, though
[14:20:27] <Reedy>	 >$wiki = WikiMap::getWiki( WikiMap::getCurrentWikiId() );
[14:20:37] <Reedy>	 That function call is returning null
[14:22:09] <Reedy>	 >	 * @return WikiReference|null WikiReference object or null if the wiki was not found
[14:22:32] <ArrakeenMiner>	 hmm, okay, I don't get why because the settings all seem to be fine :O
[14:22:46] <Reedy>	 They're presumably not then
[14:26:22] <ArrakeenMiner>	 hmmm interesting
[14:27:13] <Reedy>	 Why are you setting  $wgConf->settings multiple times?
[14:28:16] <Reedy>	 Also, don't use "?>" at the end
[14:28:20] <ArrakeenMiner>	 I followed the walkthrough for the installation of the extension — doesn't seem to be an issue when using a GSS and separate LocalSettings files but just won't work presently
[14:30:28] <ArrakeenMiner>	 (I've removed the duplicates $wgConf->settings)
[14:44:44] <ArrakeenMiner>	 I'm pretty sure the set up is right considering it works with separate LS.php files, it just won't work combined for some reason
[14:46:51] <Reedy>	 If it doesn't work, it's not right :)
[14:47:42] <ArrakeenMiner>	 okay I figured it out, there were some residual settings from a different extension interfering:P
[14:59:16] <Reedy>	 lol
[21:46:34] <digimer>	 Hi all, I added: wfLoadExtension( 'SyntaxHighlight_GeSHi' );
[21:47:11] <digimer>	 to my LocalSettings.php file, and reloaded apache (and it's in my extensions folder), it's not working yet. Is there a way to see what extensions are enabled?
[21:47:38] <Reedy>	 Special:Version
[21:47:43] <Reedy>	 What do you mean it's not working though?
[21:48:14] <digimer>	 I see it's enabled (version 2).
[21:48:45] <digimer>	 "Not working" as it the <syntaxhighlight lang="bash> ... </syntaxhighlight> shows the tags as if they're normal text
[21:49:04] <digimer>	 if you're curious; https://www.digimer.ca/w/index.php?title=Boat_Router#Wireless_Interface
[21:49:38] <Reedy>	 Unrelated, but you're behind on your patches for MW core ;)
[21:49:51] <digimer>	 noted
[21:50:04] <Reedy>	 But it'll be even more out of date later this week (1.37.3 will be out)
[21:50:18] <digimer>	 I'll make a note to update
[21:51:08] <Reedy>	 Can you purge/null edit the page?
[21:51:13] <bd808>	 digimer: you needed to reparse the page. I did an `?action=purge` and it;s kind of working
[21:51:29] <bd808>	 errr.. or maybe not
[21:51:34] <digimer>	 I'm sorry, how do I reparse a page?
[21:51:48] <Reedy>	 you can click edit, make no changes and just click save
[21:51:58] <Reedy>	 or append &action=purge to the url
[21:52:00] <digimer>	 done, no change
[21:52:10] <Reedy>	 !debug
[21:52:10] <wm-bot>	 For information on debugging (including viewing errors), see https://mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging Also see https://mediawiki.org/wiki/Manual:Errors_and_symptoms
[21:52:22] <digimer>	 purged, still not working
[21:53:37] <digimer>	 restarting memcache fixed it
[21:53:59] <Reedy>	 sounds like your caching is a bit flaky
[21:54:16] <digimer>	 now on the topic of being behind; Is there a command line tool (linux, centos) to update an install? Or do I need to redownload the source?
[21:54:43] <Reedy>	 Depends how you installed it
[21:55:06] <Reedy>	 If you installed using a package (which we don't generally recommend), you can get it from your package manager
[21:55:09] <digimer>	 Downloaded the tarball, extracted it in my apache /var/www/<url>/html page
[21:55:14] <digimer>	 directory* 
[21:55:15] <Reedy>	 If you installed it using git clone, change the tag
[21:55:30] <Reedy>	 If you grabbed a tarball, we do publish patches for point releases
[21:55:49] <Reedy>	 https://lists.wikimedia.org/hyperkitty/list/mediawiki-announce@lists.wikimedia.org/message/YJNXKPV5Z56NSUQ4G3SXPDUIZG5EQ7UR/
[21:55:51] <digimer>	 that's nice :) So I should be able to update without downloading again?
[21:55:56] <digimer>	 <reading...>
[21:57:57] <digimer>	 I downloaded mediawiki-1.37.2.patch, but I'm not super familiar with using patches. Is there a guide on how to use it?
[21:59:25] <Reedy>	 I don't know how well we have it documented, as it's just the linux patch tool (gunzip and apply!)
[22:05:40] <digimer>	 got it
[22:06:02] <digimer>	 future reference; Copy the patch to the base directory mediawiki is installed in, then test run with: patch -p1 --dry-run -i mediawiki-1.37.2.patch 
[22:06:11] <digimer>	 if that works, run again without --dry-run
[22:06:45] <digimer>	 https://www.mediawiki.org/wiki/Manual:Upgrading -> "Using patch
[22:07:09] <digimer>	 ok, back to my documenting, thank you kindly, Reedy