[11:56:26] <sejalkore>	 hiii
[13:20:11] <Jhs->	 Hi! I am upgrading a wiki from 1.31 to 1.35. When doing upgrades like this, when you're upgrading more than 1 version, is there an easy way to get a list of things one should be extra aware of? There have been several database schema changes that are causing some issues
[13:21:24] <Jhs->	 Also: https://www.mediawiki.org/wiki/Manual:MigrateComments.php seems like a current script. However, it says "$wgCommentTableSchemaMigrationStage needs to be set to MIGRATION_WRITE_NEW or MIGRATION_NEW for the script to do the migration.". But when I go to https://www.mediawiki.org/wiki/Manual:$wgCommentTableSchemaMigrationStage , it says "This feature was removed completely in version 1.33.0."
[13:21:44] <Jhs->	 so which is it? Should I set $wgCommentTableSchemaMigrationStage or not?
[13:27:32] * hetti sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/kocehweWENkKNCkWaQpZUIhA/message.txt >
[13:28:15] <hetti>	 At least I didn't encountered any faults except some Extension stuff
[16:52:11] <rjw>	 hello. i've just upgraded an old wiki from 1.27.7 (old LTS) to the latest LTS 1.35.1. Everything went smoothly, post upgrade the wiki is up and running but I'm unable to make edits
[16:52:35] <rjw>	 the error im getting is:
[16:52:37] <rjw>	 Error 19: UNIQUE constraint failed: slots.slot_revision_id, slots.slot_role_id
[16:52:46] <rjw>	 Function: MediaWiki\Revision\RevisionStore::insertSlotRowOn
[16:52:56] <rjw>	 Query: INSERT INTO slots (slot_revision_id,slot_role_id,slot_content_id,slot_origin) VALUES (19988,1,19905,19988)
[16:53:07] <rjw>	 then the backtrace, etc
[16:55:06] <rjw>	 the schema and error are pasted here:
[16:55:08] <rjw>	 https://pastebin.com/urGGacLz
[17:00:07] <rjw>	 select * from slots where slot_revision_id='19988';
[17:00:07] <rjw>	 19988|1|19904|19988
[17:01:04] <rjw>	 thats a primary key, so I guess makes sense that its failing.
[17:01:34] <rjw>	 but it seems to want to insert the same data into slots no matter what page i attempt to edit
[18:39:45] <Vulpix>	 rjw: can you check your slot_roles table? It should have the role_id 1 at least
[18:40:50] <rjw>	 yea thats all it has
[18:40:58] <rjw>	 select * from slot_roles;
[18:40:58] <rjw>	 1|main
[18:41:52] <rjw>	 .schema slot_roles
[18:41:52] <rjw>	 CREATE TABLE slot_roles (
[18:41:53] <rjw>	  role_id INTEGER PRIMARY KEY AUTOINCREMENT,
[18:41:53] <rjw>	  role_name BLOB NOT NULL
[18:41:54] <rjw>	  );
[18:41:55] <rjw>	 CREATE UNIQUE INDEX role_name ON slot_roles (role_name)
[18:41:55] <rjw>	 ;
[18:46:03] <rjw>	 how does it decide what slot_revision_id to use? i noticed the highest rev_id in the revision table is 19987, one less than what its trying to add to slot_revision_id
[18:46:32] <rjw>	 i've never really looked at mediawiki db internals before
[18:47:44] <hetti>	 try to run
[18:47:47] <hetti>	 Run populateContentTables.php
[18:47:47] <hetti>	  and then update.php again
[18:49:57] <rjw>	 Populating revision...
[18:49:58] <rjw>	 No need to populate, revision.rev_text_id field does not exist
[18:49:58] <rjw>	 Populating archive...
[18:49:59] <rjw>	 No need to populate, archive.ar_text_id field does not exist
[18:49:59] <rjw>	 Done. Processed 0 rows in 0.059148073196411 seconds
[18:50:24] <rjw>	 update ran through quickly:
[18:50:25] <rjw>	 Done in 1.0 s.
[18:50:33] <rjw>	 same issue still exists
[18:50:57] <hetti>	 :(
[18:57:38] <rjw>	 hope i didnt miss anything, got timed out
[18:57:53] <hetti>	 no u didn't
[19:00:17] <rjw>	 thnx
[19:01:22] <hetti>	 what you could try is a in between upgrade if it is for example broken on 1.31 or so
[19:01:49] <hetti>	 and if this works, upgrade on 1.35 should work
[19:02:01] <hetti>	 at least my theory
[19:08:46] <rjw>	 thanks. maybe i'll give that a go if i dont have anything else to try
[19:08:55] <rjw>	 rather not back everything out if i dont have to
[19:09:53] * hetti sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/qswbNVyuHwaOtOklPjeCmLLm/message.txt >
[19:10:16] <hetti>	 and also automated everything with ansible, now setting up a the wiki is just a couple of minutes for now and future stuff
[19:33:35] <rjw>	 i restored the oriignal 1.27 db, ran the 1.31 update on it, then ran the 1.35. same issue.
[19:35:53] <rjw>	 guess i can start over and begin with 1.29, that worked for you
[19:36:07] <rjw>	 ah well you started with 1.29
[19:36:22] <rjw>	 cant hurt to try i guess
[19:41:10] <Krinkle>	 subbu: random q - is Parsoid/JS still in prod? https://phabricator.wikimedia.org/T241202
[19:46:05] <subbu>	 not sure if it has been undeployed .. i don't think there is anything blocking it.
[19:48:15] <rjw>	 same issue 1.27 -> 1.29 -> 1.35
[20:42:06] <hetti>	 Yes I started from 1.29
[20:42:09] <hetti>	 :S
[20:44:06] <rjw>	 doing a fresh install of 1.35 and then restoring the xml from dump worked ok
[20:44:09] <rjw>	 but i am missing images
[20:44:41] <rjw>	 importImages.php /path/to/mediawiki/images doesnt work
[20:44:57] <rjw>	 Importing Files
[20:44:57] <rjw>	 No suitable files could be found for import.
[20:45:08] <rjw>	 images is the dir from the old install
[20:45:29] <rjw>	 ## To enable image uploads, make sure the 'images' directory
[20:45:30] <rjw>	 ## is writable, then set this to true:
[20:45:30] <rjw>	 $wgEnableUploads  = true;
[20:45:31] <rjw>	 $wgUseImageMagick = true;
[20:45:31] <rjw>	 $wgImageMagickConvertCommand = "/usr/bin/convert";
[20:45:32] <rjw>	 $wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'pdf' );
[20:45:36] <rjw>	 also was using
[20:45:36] <rjw>	 $wgHashedUploadDirectory = true;
[20:45:45] <rjw>	 brb
[21:15:04] <kaste_>	 Hi, I am trying to work out what the currently supported way to use google as my user authenticator is. There seem to be many different ways, but the only ones with semi comprehensive documentation, are all deprecated apparently
[21:16:04] <kaste_>	 Where should I start reading for the best way?
[21:17:07] <kaste_>	 It's a private wiki and I want to use the users defined by the Gsuite accounts, ideally with SSO if possible.
[21:26:17] <Skizzerz>	 kaste_: the WSOAuth extension is probably your best bet, but looks like google auth support isn't baked into it so you'd need to develop an auth provider for it
[21:27:13] <tgr_>	 what's wrong with GoogleLogin?
[21:28:07] <Skizzerz>	 tgr_: thought it was authplugin based still, not authmanager
[21:28:14] <Skizzerz>	 looks like that's not the case, so that's something to check out too :)
[21:28:35] <tgr_>	 it's by far the most feature-rich authmanager extension I have seen
[21:29:08] <kaste_>	 https://www.mediawiki.org/wiki/Extension:GoogleLogin/PreAuthManager/en I understood that to mean, it's deprecated
[21:29:39] <kaste_>	 is that the one?
[21:29:56] <Skizzerz>	 kaste_: that's an archived version of the extension page. You want https://www.mediawiki.org/wiki/Extension:GoogleLogin
[21:30:09] <kaste_>	 ahhh, thanks
[21:30:13] <kaste_>	 Not sure how I missed that one