[03:28:08] Not able to create account [06:01:32] I am facing a strange issue with Math extension. I can see from the inspector that the SVG of the formula is generated... But for some reason it wont display! Anyone know a patch for this? It had several other issues, but this - https://phabricator.wikimedia.org/T113708 fixed some. [06:39:08] I am making a POST request in a test script in pywikibot (using urllib2), and I am getting the error: "code":"badtoken","info":"Invalid token" [06:39:21] The value of the token is 56fb8d7338c32b1aa4cd6aa9ceefa9dd575bb0ff+\ - where am I going wrong? [06:39:35] Here's the code: http://paste.ubuntu.com/17199874/ [09:41:43] Hi all. What's the recommended method to style the templates? I was advised several times to inline all the styles for a template and not add it in the skin css. Is that the recommended way? [09:58:56] pipestash: That's how it's done currently on Wikipedia but there's a new extension that lets you use stylesheets in templates. [09:59:02] http://mediawiki.org/wiki/Extension:TemplateStyles [10:02:34] Glaisher, thank your letting me know about this. However, how will this work incase of templates that have different styles. And indeed, now I am able to understand why inline style is recommended. :) [11:14:52] I've started filling https://bestpractices.coreinfrastructure.org/projects/201 [12:16:20] hey guys [12:16:36] i want to know that does mediawiki API provides CSS and JS ? [12:27:39] anyone [12:50:31] arcade_: I don't think so. [12:52:33] ok [12:52:37] thanks for the reply [12:52:50] then i have to implement client side css :( [15:01:44] arcade_: Err, what are you doing? [15:01:58] I think most people use ResourceLoader and have no troubles serving CSS and JS. [15:02:02] Or you can use wiki pages, if you want. [15:02:25] It may not be served via api.php, you may need to use index.php or load.php. But the general principles are the same. [15:02:45] Oh well. [15:35:59] Hi! running mediawiki 1.26. how can I add a meta tag? the docs dictate using `$out->addMeta` for older versions, and resource loader for newer ones. and resource loader requires gadgets for 1.26+. surely there is an easier way? [15:36:12] sorry for repeat post. just a polite bump :) [15:37:13] I don't think meta tags are set by resource loader [15:37:55] awal: Where does it say addMeta() should be used for older versions? [15:46:18] What will happen if page A includes {{:B}} and page B includes {{:A}}? [15:49:18] Answer: https://meta.wikimedia.org/wiki/Help:Template [16:06:52] AFternoon all. [16:07:54] I have a quandry. I am trying to get some images uploaded onto a wiki. Everything uploads fine, no issues. And the images display when at full size. But when I try to resize them via the MW syntax, they don't display. I have a second wiki on this same hosting, with the same setup, and it doesn't have the same issue. [16:15:15] Aha, found it! ImageMagick issue. [16:22:49] I love it when people come in here asking something and find it by themselves not long after. Yay, our docs aren't that bad. :) [16:47:42] Glaisher: over here - https://www.mediawiki.org/wiki/Manual:Hooks/BeforePageDisplay [16:52:47] awal: Well addModules() cannot be used to add meta tags [16:53:32] $out->addMeta and $out->addKeyword should probably be in a separate list there since it's sort of confusing [16:53:45] Glaisher: makes sense, thanks. [20:59:26] Nemo_bis: Did you have a page in mw.org in mind for documenting the CII best practices page? [21:16:37] bawolff: no, I think the relevant pages should document each piece [21:16:57] especially the (already abundant) pages on continuous integration and security [21:17:09] I'm thinking of creating [[Core Infrastructure Initiative Best Practices badge]] [21:17:25] Actually, I got distracted and am trying to recreate their badge in css [21:17:36] That's ok but I wouldn't make it yet another page where to duplicate development guidelines FWIW [21:17:41] Hah! [21:18:14] https://www.mediawiki.org/wiki/Core_Infrastructure_Initiative_Best_Practices_badge is my attempt to recreate the badge [21:18:19] I'm kind of proud [21:19:33] I think having a central place to list the stuff we aren't yet doing might be a good idea [21:19:50] Quite good! [21:20:09] It also provides yet another opportunity to discuss about usage of grey on Wikimedia wikis! [21:20:12] for the stuff we are doing, I think it makes sense to document those on pages about the relavent topic [21:20:20] Good point [21:20:36] But I'm not yet sure what we're really not yet doing [21:21:11] Do you know why they complain about: X-Content-Type-Options was not set to "nosniff". [21:26:26] bawolff: I've also added the first proposed "rejection" on talk page, as an example [21:29:31] For keylengths, that's mostly the lower layer's (openSSL) problem [21:30:03] although I guess the hash length part kind of applies to us [21:30:53] Yeah, I think they had openssl in mind when they wrote that [21:31:46] (In fact the whole initiative seems an exercise to defend FLOSS from the FUD "see, openssl ruined the world".) [21:32:11] The subject page already begins to be useful, thanks [21:46:59] Yet another silly openssl bug hit the web today actually [21:47:30] My reading about their comment with X-Content-Type-Options: nosniff, is that they want the header there [22:46:47] hi, is it somehow possible to have a different sidebar for some given namespace? [22:50:37] probably best done with a custom extension [22:51:12] although may be possible in a really hacky fashion using parser functions {{#ifeq:{{NAMESPACE.... (Provided there are no newlines) [22:51:13] auvajs: the actual html and style of a sidebar is skin based usually, but you might be able to create an extension to modify the links given. Because skins just take an array of links and then output them for the sidebars [22:53:40] Just take a look at the vector skin and see where it generates the sidebar, then work your way back from there [22:54:45] CZauX: I'm not a programmer or webdeveloper, I'm not able to make an extension :) but I'll try bawolff's way, tnx :) be right back [22:55:35] Ah, I would say you could become one ;), but mediawiki gets confusing real quick. [22:56:30] Though, it certainly is possible if you really want it. [22:56:36] CZauX: no, I'm a lawyer :) [22:57:10] ahhh, very nice. [22:57:16] my wiki is legal dictionary [22:58:14] **{{#ifeq:{{ns:{{NAMESPACENUMBER}}}}|{{ns:Talk}}|page to link{{!}}text if talk ns|page to link{{!}}text for non-talk}} [22:58:21] is what you basically have to do [22:58:49] which is super hacky [22:58:52] bawolff: yeah, I'll just finish something different and have a look at it, tnx [22:59:10] *somehing else [22:59:44] * bawolff makes no garuntee this will always work, but its worked for a while now [23:00:04] also, its incompatible with $wgEnableSidebarCache. But that's off by default [23:09:11] bawolff: in your example, should I replace {{NAMESPACENUMBER}} with the number? so it starts with **{{#ifeq:{{ns:304}}| ? [23:09:40] no, replace the {{ns:Talk}} with {{ns:Name of namespace}} [23:09:55] {{NAMESPACENUMBER}} stands in for the current namespace being viewed [23:10:12] If you want to use numbers directly, you can do [23:10:22] ah I get it [23:10:46] **{{#ifeq:{{NAMESPACENUMBER}}|304|page to link if in 304{{!}}text if ns is 304|page to link{{!}}text for non-304}} [23:11:12] If you want to chose from among more than one namespace you can use #switch [23:11:33] I'm assuming your wiki has the ParserFunctions extension installed [23:12:44] seems to be working, tnx :)) [23:17:27] some way how to make this work for headings too? [23:17:34] {{#ifeq:{{NAMESPACENUMBER}}|304|* Trestné činy}} sth like that [23:18:08] so that this heading is shown only in ns 304