[04:54:19] is there any way to prevent a specific user from being able to use the reset password function? got a mod who is apparently being harrassed by someone who is (among other things) spamming the reset password function... [04:56:07] it's like a mini DoS attack [05:19:07] No_one_at_all: nope. I suggest temporarily blocking their IP at the firewall level [05:19:28] bleh. [06:17:20] If the admins email isn't public/known to the attacker... [06:17:26] They can enable "Send password reset emails only when both email address and username are provided." [06:17:46] Special:Preferences#mw-prefsection-personal-email [07:33:27] Hello all [07:33:41] Can I ask something [07:34:18] syma: I would recommend that you not ask to ask, just ask. [07:34:52] syma: People here help as they are able, so when they see your question, and if they have an answer, they will answer. [07:35:10] Thanks waggie [07:37:24] In $wgCentralAuthCookieDomain I get doubt, how to make a cookie on two different domain .wiki.org and .wikipedia.org with different subdomain, how to write two domain in there? Reference https://github.com/wikimedia/mediawiki-extensions-CentralAuth/blob/master/CentralAuth.php [07:38:10] I getting error logging and signup [07:40:41] syma: you can use $wgCentralAuthAutoLoginWikis to automatically login on multiple domains, see https://www.mediawiki.org/wiki/Extension:CentralAuth [07:41:46] note that CentralAuth is kind of a mess and I wouldn't recommend using it unless you are willing and know how to tinker with it if it breaks [07:44:53] Thanks majava for statement, I breaks which we have two domain name and if I use centralauthloginwiki if appears no loging sessions [07:45:24] It appears no logging session [07:47:28] you need to be more specific on how it "breaks". are there any error messages? anything in browser console? what did you set the config value to? what do you use for session storage? [07:48:37] did you set up the dedicated login wiki? [07:52:05] Sorry majavah, I will complete the detail [15:49:47] Hi. I've set $wgLogos to ['icon' => $wgScriptPath . "/images/logo.svg"], but the logo is not showing up. Why. The favicon works $wgFavicon = "$wgScriptPath/images/favicon.svg"; [15:53:06] Have you looked at the output HTML/CSS? [15:55:04] Reedy: It's still background-image: url(/wiki/resources/assets/wiki.png?86a63); [15:58:49] lenarhoyt: have you tried setting '1x' instead of 'icon'? [16:03:10] Vulpix: ah 1x and 2x works [16:03:18] Vulpix: but they are depricated, right? [16:03:33] !wg Logos [16:03:33] https://www.mediawiki.org/wiki/Manual:%24wgLogos [16:04:11] Vulpix: Vulpix: maybe my SVG should be exactly 50x50? [16:04:25] Vulpix: it is currently 270x270 [16:04:43] deprecation policies affect skin developers. Maybe the skin you use hasn't been updated to use 'icon' [16:05:26] Nor is it well/consistently documented... [16:05:26] T274900 [16:05:27] T274900: $wgLogos DefaultSettings.php documentation mismatch - https://phabricator.wikimedia.org/T274900 [16:06:55] Vulpix: it is default Vector [16:11:00] File a bug report, then :P [21:34:03] Jon Robson Did we change anything recently relating to interface-admin vs administrator user right permissioning? [21:34:40] I ask because some users have suddenly stopped seeing interface-admin restricted interface elements on French Wikipedia on the page protection form. [21:34:55] However it looks like nothing relating to permissioning has changed in the page protection form [21:35:53] Vulpix: in terms of logo it depends on the skin. Historically skins have provided their own configuration for logos and we're slowly trying to move towards a logo configuration that works for all skins [21:36:37] For example timeless and Minerva use the $wgLogos['wordmark'] and $wgLogos['icon'] for their logo. Monobook and Vector uses '1x'. [21:37:02] `1x` is only deprecated for new skins but that's gonna take time, better docs and more communication like this :).