[13:38:25] morning [13:42:43] Morning. [14:11:19] is there documentation available what filesystem permissions mediawiki requires? or a check that tells me if all permissions are correct? atm, all mediawiki files are owned by root and are not writable by the web server user. [14:21:43] Anyway to see what .css I can edit on the wiki I run? My skin doesn't have a .css and Common.css isn't changing everything on the wiki. [17:33:46] !debug [17:33:46] For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging [17:59:42] In Special:Notifications I see Notifications but in the Menubar I dont. Do you know why? [18:07:27] Hello, I have an issue [18:07:49] I'm also seeking some information [18:08:04] On how wikipedia determines who is and is not authorized to speak about their own lives [18:08:15] *biographies on Wikipedia [18:09:46] I think, generally, people shouldn't edit pages about them [18:09:53] gab__: you might get a better response on #wikipedia-en. but generally, no one. :) [18:10:53] what is wikipedia-en [18:10:56] and how do I talk to them [18:11:09] /join #wikipedia-en [19:49:14] Hello there, I'm having a little issue with the FlaggedRevs extension, it is not showing the stable version as default for logged in users, even with Override=true and Exceptions = array(); [19:50:34] could anyone help me, I've tryed to debug the returns of FlaggedWikiPage:isStableShownByDefault(), but its always true and it doesn't change the behavior [20:47:10] mediawiki isn't logging [20:47:31] Logfile set with $wgDebugLogFile [20:47:50] PHP logging set with error_reporting and ini_set [20:47:59] are privileges all right? [20:48:01] Folder chowned to www-data [20:48:12] www-data:www-data [20:49:10] I'm trying to debug xyGraphicalCategoryBrowser [20:49:37] It just isn't displaying the graph, package is installed, localsettings line is there [20:49:44] No error on the page [21:28:39] greeting, I have a quick question, I might just need better keywords more than anything else, but I might be mistaken ... anyway, I'm looking for a sane way to create a pre-configured mediawiki; i want to have certain pages and possibly certain plugins pre-installed. do I fork mediawiki? is there a way to keep the vanilla mediawiki outside such configuration? [21:47:18] uwe: are you comfortable using vagrant? [21:47:50] https://www.mediawiki.org/wiki/MediaWiki-Vagrant [21:48:38] you could grab the base image, enable whatever roles and do whatever configuration you want, and then distribute the modified image [21:49:35] otherwise, you could ship just a regular mediawiki distribution alongside whatever extensions you want to bundle, but that won't get pages or the database set up with stuff by default [21:50:12] hmmm, AlvaroMolina , I've played a bit with it before, but I'm not trying to maintain an instance, rather than create a distribution/configuration profile, and allow people to download it as if it was a modified mediawiki, or download mediawiki then "do something" and it'll be configured for them in a certain way [21:51:59] maybe i should maintain a script/batches or just a .tgz file with the extensions and stuff ... but it sounds not too neat ... if you happen to only have ftp access for instance ... [21:52:12] sorry, i ment Skizzerz [21:53:23] uwe: Do not worry. :) [21:53:55] I guess you are suggesting that there is no easy way to do so; content + extensions [21:53:59] the thing is, if you only distribute the source code, the end user must still run the installer themselves to set up database info, etc. [21:54:35] they can enable bundled extensions as part of the installer, and perhaps one of your extensions could then create the needed content when enabled [21:54:46] but the user will need to know to do those steps [21:55:40] it's not an insurmountable challenge, but it isn't completely foolproof either [21:56:11] Skizzerz: yes yes, Its a "normal" setup ... where a whole bunch of extensions would be pre-enabled [21:56:15] you can accomplish everything you want via extensions though, you don't need to modify the core files [21:56:28] the pre-enabled is the tricky part [21:56:46] the installer doesn't pre-enable any bundled extensions iirc, the user must select them all manually [21:56:49] so maintain content as an extension ... and figure out how to pre-enable the extensions [21:57:25] the extension for the content would simply have installer/upgrader hooks to insert the necessary content [21:57:57] (using the same underlying hook points that allows extensions to register their own database tables) [22:06:40] Thank you Skizzerz [22:24:36] Email shoulda mentioned the new PHP requirement, IMHO. That's a deal breaker for a lot of people. [22:25:10] I hadn't thought of that in the announcement. It's at the very top of the release notes at least :\ [22:25:13] On wiki and file [22:25:34] Not being able to run MW on an old insecure php version but is a deal breaker? [22:27:45] I don't think https://www.mediawiki.org/wiki/Module:Version works right with 4 active versions or two lts's or something [22:27:58] Yes: those places using one of the LTS OSs (which do patch their PHPs) [22:28:41] Oh well, that's fixed in 2 minutes anyway when I EOL 1.25 [22:28:41] (I'm not fighting the decision, just pointing out it's more important than AuthManager :) [22:30:57] -- Is there a beta branch that isn't a proper release yet? [22:30:57] p.isthereabeta = true [22:31:27] hrm [22:34:13] * legoktm grumbles at https://www.mediawiki.org/w/index.php?title=Template:MW_legacy_lts_release_git&action=edit [22:42:30] Yeah it doesn't fix the lts bit but removing 1.25.x fixed the alpha branch as 1.28 instead of 1.29 [22:43:39] I'll look at the LTS thing in a little bit [22:56:46] lol [22:56:48] https://www.mediawiki.org/w/index.php?title=Version_lifecycle&action=history [22:57:04] colors and non-automatic tables are hard lol [22:58:50] see ostriches, that's why we invented visualeditor [22:58:56] oh gods, it has translate too. disregard that [22:59:27] i probably did everything wrong lol [22:59:47] MatmaRex: Ideally it just uses the templates and modules and nobody has to update it [22:59:52] Updating it would be silly :) [22:59:53] also these are some terrible colors D: [23:00:02] I didn't make the table! [23:02:09] ostriches: I kind of fixed module:version and also broke it. I think we need a mode for 'lts' and 'legacy lts' or something