[08:41:35] <GPEquinox>	 Hi! How do I check if a particular article has been moved without a redirect left behind?
[08:41:58] <GPEquinox>	 I looked at https://www.mediawiki.org/wiki/Manual:Logging_table to see if the log_page column in logging table would be of any use
[08:42:03] <RhinosF1>	 Special:Log
[08:42:12] <GPEquinox>	 but here is what the docs say: The page_id that this log action is about. Comparable to rc_cur_id and rev_page. In the case of a page move, this is set to the page_id of the moved page (since Gerrit change 157872). Formerly, it was the page_id of the redirect, or 0 if the page was moved without creating a redirect.
[08:42:30] <GPEquinox>	 i wanna do this in the PHP backend, so what param should I check for?
[08:42:34] <RhinosF1>	 log_type will be move
[08:42:50] <GPEquinox>	 correct, that'd include the ones that have been moved with a redirect too, right?
[08:42:58] <RhinosF1>	 yep
[08:43:03] <RhinosF1>	 but why use the backend
[08:43:20] <GPEquinox>	 it's a maintenance script, pretty unique use cae
[08:43:21] <GPEquinox>	 case*
[08:43:26] <GPEquinox>	 i get why Special:Log is great
[08:43:45] <GPEquinox>	 but I need to do this via a PHP maintenance script
[08:44:13] <GPEquinox>	 hence, do you know if I can differentiate between the two types of moved articles (with and without redirect) by just looking at logging table?
[08:44:17] <GPEquinox>	 or any other mechanism?
[08:45:09] <RhinosF1>	 there will be a way
[08:45:52] <RhinosF1>	 log_actions should do
[08:45:57] <GPEquinox>	 yea, i expect there is an easy way to do this
[08:46:29] <GPEquinox>	 hm let me check that out
[08:46:36] <GPEquinox>	 I appreciate your help, thanks
[09:10:39] <hallstein>	 Hello! I'm new to mediawiki. Trying to set it up as an Azure app running the docker image (https://hub.docker.com/_/mediawiki) and MariaDB. When performing the installation steps, it fails during the database install, with error message:
[09:11:06] <hallstein>	 [18209ffacb697baad67f599c] /mw-config/index.php?page=Install Wikimedia\Rdbms\DBQueryError from line 1699 of /var/www/html/includes/libs/rdbms/database/Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?
[09:11:07] <hallstein>	 Error 1005: Can't create table `wiki`.`searchindex` (errno: 1 "Operation not permitted") (xwiki.mariadb.database.azure.com)
[09:11:07] <hallstein>	 Function: Wikimedia\Rdbms\Database::sourceFile( /var/www/html/maintenance/tables.sql )
[09:11:08] <hallstein>	 Query: CREATE TABLE `searchindex` (
[09:11:08] <hallstein>	 si_page int unsigned NOT NULL,
[09:11:09] <hallstein>	 si_title varchar(255) NOT NULL default '',
[09:11:09] <hallstein>	 si_text mediumtext NOT NULL
[09:11:10] <hallstein>	 ) ENGINE=MyISAM DEFAULT CHARSET=utf8
[09:11:12] <hallstein>	 Anyone?
[09:12:13] <Majavah>	 first, use a pastebin instead of copy pasting multiple lines, otherwise the network might kick you out
[09:12:24] <Majavah>	 second, what grants does the database user have?
[09:12:27] <hallstein>	 oh, sorry
[09:13:53] <hallstein>	 The user should have all grants.
[09:14:38] <GPEquinox>	 hallstein - Could it be because Azure supports only innoDB type storage engine
[09:14:41] <GPEquinox>	 i think
[09:15:09] <GPEquinox>	 doesn't support aria storage enginer
[09:16:01] <GPEquinox>	 or maybe this - https://stackoverflow.com/questions/12623651/error-error-1005-cant-create-table-errno-121
[09:16:23] <Majavah>	 https://docs.microsoft.com/en-us/azure/mysql/concepts-limits#unsupported
[09:16:56] <GPEquinox>	 https://docs.microsoft.com/en-us/azure/dms/known-issues-azure-mysql-online
[09:21:23] <hallstein>	 Ok, so what you're saying is that using Azure + mediawiki docker image + Azure MySQL/MariaDB is not possible.. so if I want this hosted in Azure, I need to use a VM?
[09:23:46] <GPEquinox>	 can you try using MySQL instead of MariaDB?
[09:24:05] <GPEquinox>	 in case the error is due to an incompatible MariaDB storage engine
[09:24:13] <Majavah>	 when configuring the database it should let you choose to use InnoDB instead of MyISAM
[09:24:18] <GPEquinox>	 Azure + MediaWiki + some compatible DB should work, according to me
[09:24:47] <GPEquinox>	 I just want you to make sure you're using InnoDB as the storage engine
[09:25:26] <GPEquinox>	 since the error msg that you pasted has engine = MyISAM
[09:25:42] <GPEquinox>	 i'd recommend trying to re-install with MariaDB/ MySQL with InnoDB as the storage enginer
[09:25:47] <GPEquinox>	 and not MyISAM
[09:26:30] <GPEquinox>	 fyi, in case you wanna learn about DB storage engines:  https://www.w3resource.com/mysql/mysql-storage-engines.php
[09:27:18] <GPEquinox>	 if you look at the Azure's documentation
[09:27:20] <GPEquinox>	 here: https://docs.microsoft.com/en-us/azure/mysql/concepts-limits
[09:27:29] <GPEquinox>	 you'll seee that they don't support MyISAM engine
[09:27:46] <GPEquinox>	 however, they do support the InnoDB engine (which is usually the default engine for MySQL)
[09:28:02] <GPEquinox>	 so, changing your installation to a MySQL/ MariaDB whhich uses InnoDB engine
[09:28:03] <GPEquinox>	 should work
[09:28:09] <GPEquinox>	 instead of the MyISAM
[09:28:21] <GPEquinox>	 does that make sense? let me know, happy to help further
[09:31:15] <hallstein>	 Thanks a lot for helping me out! As far as I can see, Azure only supports InnoDB for MariaDB. Also, if I run `SHOW TABLE STATUS FROM `wiki`;` the Engine column states "InnoDB".
[09:32:01] <hallstein>	 Which makes it weird that the mediawiki-installation uses myisam?
[09:32:07] <GPEquinox>	 idk why MediaWiki is trying to install the searchindex table with MyISAM
[09:32:31] <GPEquinox>	 I think MyISAM helps with text searching, etc.
[09:32:33] <Majavah>	 hallstein: did you manage to complete the installation yet?
[09:32:37] <GPEquinox>	 and the table name searchindex
[09:32:45] <hallstein>	 Majavah No
[09:33:19] <Majavah>	 did you choose InnoDB or MyISQM when configuring the database details?
[09:33:59] <GPEquinox>	 Also hallstein - the query failure happened while creating the table searchindex
[09:34:44] <GPEquinox>	 so, if the DB installation happened in InnoDB, that tablr was still being attempted using myISAM
[09:34:45] <Majavah>	 actually this table is myisam on my wiki too, even thru everything else is innodb
[09:34:53] <GPEquinox>	 weird
[09:35:33] <hallstein>	 hmm.. I cannot see an option to change this during the installation..
[09:36:11] <GPEquinox>	 https://www.mediawiki.org/wiki/Manual:Searchindex_table
[09:36:14] <Majavah>	 this looks like a known issue in mediawiki, T107875
[09:36:15] <stashbot>	 T107875: Use InnoDB engine for searchindex table in MySQL - https://phabricator.wikimedia.org/T107875
[09:36:19] <GPEquinox>	 this table apparently needs MyISAM
[09:36:27] <GPEquinox>	 yeah, seems like a known issue
[09:36:33] <GPEquinox>	 I see other issues related to this
[09:36:49] <GPEquinox>	 I also see this: If using Postgres, this table does not exist: the full text information is stored as columns in the page and pagecontent tables directly.
[09:37:41] <GPEquinox>	 https://www.mediawiki.org/wiki/Topic:Sgtvuq71ep4mnxiu
[09:38:32] <GPEquinox>	 maybe try using postgres, if you want a MW instance up on Azure asap?
[09:38:45] <GPEquinox>	 or trying another cloud provider with support MyISAM?
[09:41:08] <hallstein>	 ok, makes sense that it doesn't work this way if MyISAM is required and Azure doesn't support it for hosted MySQL/MariaDB
[09:41:35] <GPEquinox>	 yeah, hopefully this helped make some sense of the situation
[09:41:40] <GPEquinox>	 definitely frustrating
[09:41:51] <hallstein>	 haha, agreed. well, thanks a lot guys!
[09:42:05] <GPEquinox>	 sure thing, have a good rest of your day/ night!
[09:47:35] <RhinosF1>	 Majavah: marked it as resolved linking to our task
[10:14:56] <Torsten552>	 Hi guys, is there a way to choose between different templates when creating a new article page?
[10:33:35] <ashley>	 Torsten552: not out of the box IIRC but some extensions allow that (provided you configure them appropriately), e.g. https://www.mediawiki.org/wiki/Extension:CreateAPage or https://www.mediawiki.org/wiki/Extension:Form (full disclaimer: I've contributed to both extensions in question ;)
[10:42:01] <Torsten552>	 ashley thank you
[11:15:47] <Torsten552>	 ashley CreateAPage is not working with 1.31 and Form is not what I was looking for. Do you have maybe another idea how I can choose between two or more templates when creating a page?
[11:16:29] <ashley>	 no, but CreateAPage works w/ 1.35 which is the latest stable version and also a long-term support (LTS) release, do consider upgrading  your MW :)
[11:24:51] <Torsten552>	 yeah, will do that, but not now :D
[11:24:58] <Torsten552>	 thank you again
[13:31:29] <LClightcat>	 Excuse me, who can help me?
[13:32:25] <LClightcat>	 The thing is, I want to configure the email system. What should I do?
[13:34:40] <Majavah>	 !email
[13:34:40] <wm-bot>	 For information about setting up email, see <http://www.mediawiki.org/wiki/Email#Email_settings>. For extensions, see <http://www.mediawiki.org/wiki/Category:Email_extensions>
[13:35:19] <LClightcat>	 OK, I know. Thank you!
[16:20:43] <absorto>	 Hi there, I need some help with VisualEditor. I working on a private wiki running 1.35
[16:21:08] <absorto>	 when trying to use VE it says it cannot connect with RESTbase
[16:22:36] <absorto>	 I can see on the Extension:VisualEditor page that VE should work out-of-the-box for 1.35. Am I missing something here?
[16:29:40] <RhinosF1>	 absorto: what's the exact error?
[16:33:00] <absorto>	 RhinosF1: a popup shows up saying this "Error contacting the Parsoid/RESTBase server (HTTP 400)"
[16:33:43] <RhinosF1>	 absorto: the parsoid part is for you not restbase. What exact config do you have?
[16:34:54] <absorto>	 I have not installed Parsoid as I did with previous versions because I understood it is bundled with 1.35, correct?
[16:35:37] <absorto>	 neither did I add configurations for parsoid in my LocalSettings file, assuming this was not needed for 1.35 anymore.
[16:37:58] <RhinosF1>	 wfLoadExtension('VisualEditor') should work
[16:39:22] <absorto>	 This I have done. I can see it is loaded, I can choose from VE or Source editing, but when selecting VE I get the message I sended prior after the loading bar
[16:39:36] <MatmaRex>	 for private wikis, check out this: https://www.mediawiki.org/wiki/Extension:VisualEditor#Linking_with_Parsoid_in_private_wikis
[16:44:15] <absorto>	 thanks MatmaRex. Added the configuration pointed in the article you sent, still seeing the same error unfortunately :/
[16:54:46] <absorto>	 from the logs I can see it is looking for the restBase: "ApiParsoidTrait::requestRestbase: Received HTTP 400 from RESTBase"
[16:57:24] <MatmaRex>	 it's not actually looking for RESTBase, just mentally substitute Parsoid there please. the terminology in the code is inconsistent
[16:58:10] <absorto>	 ah ok, thx for the headsup. I'll be mentally substituting then ;)
[16:59:08] <MatmaRex>	 absorto: you should be able to access the Parsoid API used by VisualEditor through your browser, at a URL like this: http://example.com/w/rest.php/example.com/v3/page/html/Main%20Page
[16:59:25] <MatmaRex>	 (replace "example.com" in both places with your domain, and replace "w/" with the right path if it's different)
[16:59:53] <MatmaRex>	 you'll probably see that fail with a HTTP 400 error. i don't know why that would happen, but hopefully this brings you closer to debugging it
[17:01:16] <MatmaRex>	 (i'll be away for a while now, sorry. and good luck)
[17:02:23] <absorto>	 thank you MatmaRex. I will try that! You've been very helpful
[19:24:19] <RhinosF1>	 DannyS712: congrats on getting global watchlist deployed
[19:52:49] <DannyS712>	 thanks
[20:06:42] <GPEquinox>	 Hey! Where can I get the article ID of a deleted page?
[20:07:04] <GPEquinox>	 (more specifically - which table)
[20:07:19] <GPEquinox>	 Given that I have the title name of the deleted article
[20:07:41] <Reedy>	 archive
[20:07:51] <Reedy>	 specifically, ar_page_id
[20:12:04] <GPEquinox>	 Ah
[20:12:05] <GPEquinox>	 Thanks!