[14:44:31] Hi all. My /index.php/Special:NewFiles gallery page times out and loads nothing. /var/log/apache2/errors.log has only a Maximum execution time fatal error. Where can I get more information on what may be causing the problem? [14:45:28] Is there some maintenance script that will "clean" the gallery? [21:06:50] I've found the rebuildImages.php maintanence script. Will that script rebuild the gallery? My gallery page doesn't load. It just times out. [21:07:20] no [21:08:34] Reedy: What would cause the gallery page to fail to load. The only error I get in /var/log/apache2 is a timeout fatal error. [21:08:47] the database query took too long [21:09:15] Can I extend the time limmit to test if that is the case? [21:09:35] Should bea ble to [21:09:50] This became an issue after a server crash. [21:09:59] Are you sure your database is ok? [21:11:17] I checked the mysql logs and there are no errors or anything. Is there an integrety check to run? [21:24:03] or it's probably trying to thumbnail all the newly uploaded images [21:42:05] Hi, we're developing an extension. The extension adds a section at the bottom of each page. Ideally we would like it to be a section that's available in the TOC so users can jump straight to it or use #title links. We're however having a hard time finding the right hook to react to. Can anyone help us out or offer any advice? [22:32:58] Bert: typically the way to do that is by making your extension a parser function or tag function and then adding the content to the page as part of the parsing process; that way the TOC code will pick up on the section and add it. This does mean pages would need to be edited in order to insert that tag/parser function however [22:44:21] Reedy: mysqlcheck returns OK for all tables in the mediawiki database. Are there any mediawiki specific checks that can be run? [22:44:27] moonmoon: I see, the target audience for our extension (student associations) is already finding it difficult to get students to add anything to their wikis. So having to add a tag/template to each page is probably not going to cut it :/ [22:45:34] superboot: Does Special:NewFiles?limit=1 work ? [22:46:01] I'm not familure with that command. What does it do? [22:46:20] https://en.wikipedia.org/wiki/Special:NewFiles?limit=1 [22:46:28] limits hte number of files to 1 [22:47:32] Bert: no real good options then. You'll probably need to either use BeforePageDisplay to edit the TOC via regex or add a javascript module to dynamically add to the TOC [22:47:45] the TOC code isn't designed to be interacted with and has no hooks provided for it [22:49:31] Reedy: It does work. [22:50:13] moonmoon: that's very sad to hear, we would really like to prevent having to write javascript to change to TOC, but that's probably what it will have to be then [22:50:42] superboot: limit default is 50 [22:51:41] moonmoon: could this be something we could file a feature request for? I can imagine plenty of extension developers have pondered how to do this before [22:51:59] Reedy: It blows up at 33. 32 works fine. [22:52:19] !debug [22:52:19] 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 [22:52:28] You make it give you the SQL query printed in the HTML [22:52:53] Reedy: Ok. I'll read that. Thank you very much. [22:53:42] Bert: you can also have an automated bot like Pywikibot keep track of adding the template/tag to the bottom of every page [22:54:50] legoktm: I'm afraid the student associations won't be able to set such a thing up theirselves, and we can hardly keep tabs on bots for 20 different wikis :S [22:55:18] ah, yeah :/ [22:55:32] and getting them to keep their wikis updates is a battle [22:55:39] since it's way too hard really [22:55:52] *updated [23:06:41] Bert: you can certainly request it at https://phabricator.wikimedia.org, however I wouldn't hold my breath on it happening anytime soon [23:07:39] oh no, we've reported serious bugs before and even those can take months or years to get fixed :P [23:07:44] we know the drill xD [23:07:57] note that the table of contents I believe is stored as part of the parser cache so any hooks added to the TOC won't necessarily run every page load [23:08:17] well, so the section is consistent [23:08:22] every single page will have it [23:08:51] we want to clearly denote where the regular page content ends and the extension content starts, that's cleaner and clearer for the users [23:32:42] Reedy: I've set the $wgDebugDumpSql option to true, but I don't see any logs being generated. I've checked /var/log/{syslog,mysql/*,apache2/*} as well as journalctl. The manual says it outputs to the file specified by $wgDebugLogFile. I've also tried setting $wgDebugComments to try to get it to log to the page in the browser, but still no change. Any hints? [23:33:16] The $wgDebugLogFile remains empty. [23:35:33] Did you touch the file? [23:35:42] $wgDebugDumpSql and $wgDebugComments to true should result in the SQL queries in the HTML output [23:46:45] Reedy: I did touch teh file debug.log that $wgDebugLogFile is set to. [23:47:30] Reedy: I see no output on the wiki page. [23:47:46] Look at the HTML