[18:09:58] is there a way to force a user to reset their password on next login? :o [18:11:32] A single user? [18:11:36] yes [18:12:11] Uh theres a maint script i forget what its called [18:12:15] Let me look [18:12:36] addshore: You could make their password invalid so they have to use PasswordReset [18:12:41] That's probably the closest you'll get [18:12:55] okay, thanks! :0 [18:12:56] :) [18:16:27] addshore: theres a changepassword.php https://m.mediawiki.org/wiki/Manual:Resetting_passwords [18:16:52] More accurately https://mediawiki.org/wiki/Special:MyLanguage/Manual:changePassword.php [19:22:04] I had missed this https://techcrunch.com/2019/09/19/automattic-raises-300-million-at-3-billion-valuation-from-salesforce-ventures/ [19:22:23] "We want every website, whether it’s e-commerce or anything to be powered by WordPress. And by doing so, we’ll make sure that the web can go back to being more open, more integrated and more user-centric than it would be if proprietary platforms become dominant" [19:26:47] Oh maybe this is why stu isn't on IRC any more :) https://wptavern.com/mark-davies-joins-automattic-as-chief-financial-officer [19:30:08] wordpress uhh [19:30:30] the platform on which no one knows how to develop so that you don't go insane [19:34:36] I'm not sure #mediawiki is the best position from which to lecture other CMS on sane development :D [19:48:47] that one deserved a quip :D https://tools.wmflabs.org/bash/quip/AW3v3QrD0fjmsHBaeKMO [19:49:59] Nemo_bis: I'd have to agree with that [20:24:03] is it possible to migrate my MW from MSSQL to MySQL easily [20:49:25] stiv2k__: not "easily" but it's doable [20:50:50] Step 1 would be to get a sql dump of all of the table data (in the form of INSERT statements), but without any of the CREATE TABLE statements or other DDL stuff [20:51:56] Step 2 would be to make a fresh install in MySQL for the same mediawiki version as your MSSQL database. Whenever it asks you if you'd like to pre-populate something, say no [20:52:33] Step 3 you'll still have some records that are automatically inserted in the mysql tables, clear those out so that every table is empty [20:53:01] Finally, run the sql generated from step 1 against the mysql database. Some tables will work, others will fail. Keep fixing the syntax/values for the failures until it all imports [20:54:12] your main issue that you'll run into is any of the "binary" type columns in the mssql schema, they'll get scripted as values like 0x49d841a85729... whereas mysql just expects a regular string there -- you may want to write your own script that looks for those values in the sql files and replaces them with their string versions before doing that final step [21:13:38] Skizzerz: oof, sounds complicated [21:16:02] we are using 1.27.4, and have been noticing some issues which I think are database related, as I think mediawiki is more thoroughly tested against MySQL and not MSSQL. Maybe its worth updating to latest MW first and see if those issues are resolved [21:41:55] they aren't [21:43:15] I used to be the maintainer for the mssql compatibility layer, but haven't had the time/energy to keep it up to date for quite some time now. There's some stuff in the works that'll make it easier to support in the future, but right now it's in a very broken state [21:43:45] if you upgrade first, it's possible you'll end up breaking things more than if you migrate while still on 1.27 [21:49:19] okay [21:49:32] that was going to be my next question, which order would be best to do it [21:49:39] upgrade then migrate vs migrate then upgrade, lol [21:51:06] backup :) [21:54:07] absolutely