[08:37:57] I'm using 1.31, and am trying to knock out the deprecation warnings I get. Using Chrome's console I get a batch of warnings showing up, but it only links to the mwtrack() function, not the underlying issue. DebugToolbar shows a different deprecation, but only one. What's the best way to try to trace the deprecations that are causing the warnings to pop up? [08:38:50] Abulafia: So debug toolbar will show php deprecations, where js console show javascript deprecations. So they are totally different types of deprecations [08:39:14] Abulafia: For the javascript one, first of all try loading the page in debug mode (add either ?debug=true to the url or &debug=true to the url) [08:39:32] Then i think the console should give you a better stack trace [08:39:43] * bawolff hopes, I'm really more of a php programmer [08:40:09] often the best thing is to see what the deprecated warning is for, and grep for that function [08:40:10] bawolff, that makes good sense. For the php deprecations, how does one best trace them (outside of grepping them). I've got debug=true on, but it's simply showing the line where mwtrack() is called to say there's a deprecation, rather than a traceback. (I'm more of a php programmer too) [08:41:23] Abulafia: So php deprecations should tell you the line/function that called the deprecated function (assuming $wgDevelopmentWarnings = true; ) [08:42:57] if the warning doesn't go far enough down the stack, one helpful trick is to have the deprecated function throw an exception. Then you'll get a full stack trace [08:43:36] bawolff yes, the only php deprecation showing up shows in the console with full trace info, but for the javascript ones (that's where I've got about 28 deprecation warnings) I'm hoping to find the file/lines that are triggering the warning rather than just grepping the directory. Probably most of them are in extensions I don't maintain, but want to make sure we're keeping up to date as best we can. Good trick! I'll give that a go! [08:44:26] I should have thought of that, as I'd just finished debugging a few that threw exceptions. Thanks! [21:06:37] I would like to drop all mediawiki pages down 80px in order to add a header at the top. I looked through the extension:Header Footer, but it looks very complicated, and without an example, I don't know if this is what I want dive into or not. Can someone help me with this? [21:16:26] you could use css in MediaWiki:Common.css [21:18:34] Or possibly mediawiki:sitenotice [21:18:56] (Pantonides), was your comment for me ? [21:20:14] bawolff, I thought of sitenotice, but can I have it input an image, instead of text? I read through the extension, and couldn't figure that out. [21:20:57] Sorry, I read through PageNotice [21:27:09] Sitenotice isnt an extension but built in feature [21:27:23] its fairly limitted in what it can do [21:27:56] but its just like a normal page. So you can do [[file:foo.png]] [21:28:27] anything on the page named mediawiki:sitenotice shows up at the top of every page [21:28:34] !sitenotice [21:28:34] Sitenotice is a wiki-wide message that appears at the top of the page for all users. It is editable by users in the sysop usergroup at [[MediaWiki:Sitenotice]]. https://www.mediawiki.org/wiki/Manual:Interface/Sitenotice See also: !anonnotice [23:33:26] As I'm using version numbers to mark functionality changes in the Variables extensions, I'd like to have tags marking individual versions. Are there any guidelines about that? Is there some kind of review queue in place? [23:39:17] just a recommendation to follow https://semver.org/