[00:37:23] hey, is there a way to change the Special:PasswordReset URL? [00:37:56] or do I have to edit a template somewhere? [00:44:46] Hello [00:44:53] I have a template related question [00:46:15] I am making a new Wiki over at miraheze, and no matter what I do, I cannot get the codes to go away from my pages. I've looked everywhere, and I cannot seem to find the issue. Any help? [00:46:27] The link is https://freestateofjones.miraheze.org/wiki/State_Route_1 [00:55:08] Hi Brandon___. [00:56:03] Jesus that's a lot of templates. [00:56:08] And modules. [00:56:28] Lol, I pulled pretty much everything from Wikipedia that I thought I would need [00:56:35] Key word, thought [00:58:48] Brandon___: You see that templates are listed below the textarea when editing a page? [00:59:20] Yes, I do [00:59:24] Templates and modules. [00:59:28] So one of those is to blame... somehow. [01:00:41] Yeah, I figured that much. Those two dern codes are holding up my whole article lol. All I wanted to do was make articles about these roads on my Minecraft server, but nope, gotta have some codes poking around where they shouldn't be [01:02:32] I guess maybe https://freestateofjones.miraheze.org/wiki/Module:Infobox ? [01:03:09] Most of the battle is figuring out which line of code is responsible. [01:03:20] But these pages are pretty ratchet. [01:03:43] Yeah. I've learned that importing them isnt the cleanest [01:04:12] It was worse than this, before I realized that I had to replace my .css data with Wikipedia's data for the boxes to even format correctly [11:10:51] Help [11:11:23] . [11:11:39] whois [13:39:09] Can anyone help, I can't seem to set the time for my wiki correctly, I added '$wgLocaltimezone = "Europe/London";' and 'date_default_timezone_set( $wgLocaltimezone );' to my localsettings.php, however its still time stamping page history edits with UTC instead of Europe/London [13:44:46] Fixed, was user preference [13:47:09] I run a private wiki, where only members in certain groups can read or edit. Is there an easy way to allow a group to edit talk pages but not 'content' pages? [15:13:31] wiki_guest: yeah [15:13:51] !permissions [15:13:51] For information on customizing user access, see < http://www.mediawiki.org/wiki/Help:User_rights >. For common examples of restricting access using both rights and extensions, see < http://www.mediawiki.org/wiki/Manual:Preventing_access >. [15:15:39] wiki_guest: https://www.mediawiki.org/wiki/Manual:$wgNamespaceProtection [15:17:36] I started doing it that way, by putting protections on all non-talk namespaces and adding those rights to all the groups that can edit everything, but then I found the TalkRight extension which I think is much cleaner [15:20:06] I also slightly modified UserPageEditProtection so all users can modify their own user pages (in addition to not being able to edit other people's talk pages) [15:40:31] Any chance I can get someone to fix REL1_28's extensions checkout? [16:02:27] What's wrong with them [16:02:32] Chad fixed 2ColConflict thing in https://github.com/wikimedia/mediawiki-extensions/commit/562cc38bc8d8a8c5d997374259d684e464bb4828 [16:08:40] Reedy: then BSExtendedSearch did the same thing [16:09:03] there will probably be 2-3 more of those too [16:09:59] I think I ran into a dozen on REL1_27 last time I checked it out [16:34:34] Is it possible to make mutually exclusive groups so a member can't be added to both? [16:36:38] wiki_guest: why you should do that? [16:44:11] I have some groups that are more 'labels' than 'rights groups' and it doesn't make sense for a user to belong to "division 1" and "division 2" for ex [16:44:29] You could write an extension to do that [16:44:39] but honestly, it makes much more sense just to use social convention [16:44:57] Not everything needs a technical solution, sometimes its best to tell people 'Don't do X' [16:45:57] true, I was just wondering if there was an existing method. not worth writing new code for [16:48:12] is it possible to have one group 'inherit' permissions from another group? I know I can just copy the permissions, but it makes the rights list page large. Would using autopromote make sense? If you are in "Super Trusted" group, you get autopromoted into "Editor" group? [20:49:39] Hey all, quick question. For multiple wikis, is there any reason not to just have them all use a single Memcached instance rather than one instance per wiki? [20:51:57] justinl: off the top of my head i could see a performance problem possibly being why [20:52:53] Zppix: Currently I have 6 wikis load balanced on 4 servers, so I have 6 Memcached instances per server. [20:53:25] I'm working towards moving my wikis to AWS, so I'm trying to determine if I'll need one Elasticache instance per wiki (sized appropriately) or if I could use one big one. [20:54:17] justinl: i dont know alot about aws hardware and the related sorry. [20:54:23] justinl: one memcached instance for a wiki farm is fine as the keys automatically fragment per wiki or share globally if they can. you may need to increase the amount of memory given to it though [20:54:50] This is especially important if I decide to set up a pair of Elasticache instances for added redundancy, though I think it spans availability zones so that might be overkill. [20:55:30] Ok, so I could create one big instance and point all current and any new wikis at it since it can dynamically scale. [20:56:05] Well, actually I think its scaling is limited by the instance size. [20:58:13] legoktm: I was trying to find explicit documentation about what you're saying regarding keys but I couldn't find anything that specific on https://www.mediawiki.org/wiki/Manual:Performance_tuning or https://www.mediawiki.org/wiki/Memcached [20:59:35] * legoktm looks [21:01:24] well I can't find docs about it, but mediawiki has functions ObjectCache::makeKey() which includes the wiki's database name in the key, and then ObjectCache::makeGlobalKey() which uses the prefix "global" instead of a wiki name [21:01:55] RFC meeting starting now in #wikimedia-office: Canonical data URLs for machine readable page content [21:02:08] legoktm: Cool, that's a good start. I'll dig through the code for details. Thanks!