[05:27:17] <Poppy>	 Just now realizing I missed Tim Starling Day, dang.
[14:10:23] <faceface>	 hihi
[14:10:46] <faceface>	 my http js in a https page issue went away
[14:10:50] <faceface>	 Caching I guesss
[14:11:02] <faceface>	 browser caching...
[14:12:26] <faceface>	 So I have a cryptic question... Can I write a template 'EditMe' that I use within template X that, when X is used in a page generates a link that gets me to the edit page of X?
[14:12:44] <faceface>	 I done the edit template like this: <div style="float:right" class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit}} Edit this {{NAMESPACE}}]</div>
[14:13:11] <faceface>	 Which shows "Edit this Template" correctly in the EditMe template
[14:13:54] <faceface>	 Also works fine in the X template
[14:14:20] <faceface>	 However, when I include {{X}} in a page, it links to that pages edit page, not the templates edit pave
[14:14:23] <faceface>	 page
[14:14:27] <faceface>	 just curious if there is a way round this
[14:15:25] <faceface>	 I guess I just have to include that code in every template
[15:17:38] <Bert_2>	 Hi there, fairly technical question, we're a student organisation who offers hosting to other student organisations and we try to help them manage their websites, wikis, etc. well. One of the things we do is check automatically if they're keeping their software up-to-date and secure. With WordPress, Joomla, etc. there's only one release, the latest, of their core and their modules/plugins that's consider
[15:17:44] <Bert_2>	 ed secure, now with MediaWiki this is more complex for obvious reasons. Now we currently still just push people towards updating to the latest version all the time, but with the releases speeding up in the last few years we'd like to support the LTS versions as well and ideally just check if the release has support or not. Now the problem starts with https://www.mediawiki.org/wiki/Version_lifecycle not b
[15:17:49] <Bert_2>	 eing very parseable and there not seeming to be a version API. On top of that we can easily see here what major release is still in support, but not what the latest minor release for that version is. Anyone know of an API, more machine parseable source or a page that has all info combined?
[15:17:54] <Bert_2>	 sorry for the huge message BTW, complex situation :)
[15:20:26] <Skizzerz>	 Bert_2: I don't believe such a thing exists.
[15:20:53] <Bert_2>	 Skizzerz: so my best bet is parsing the table of end of life dates and then combining that with dir listings like https://releases.wikimedia.org/mediawiki/1.32/ ?
[15:21:18] <Skizzerz>	 I would just check when the release date itself is. Normal releases are supported for 1 year after release date, LTS is supported for 3 years after release date
[15:21:36] <Skizzerz>	 that's all the table is showing you
[15:22:05] <Bert_2>	 whether I parse release or end doesn't really make a difference when it comes to parsing https://www.mediawiki.org/wiki/Version_lifecycle
[15:22:28] <Bert_2>	 though the release has an exact date
[15:22:30] <Bert_2>	 that's nice
[15:22:45] <Bert_2>	 or is the end of life the end of the month and not the exact date?
[15:23:10] <Skizzerz>	 oh
[15:23:26] <Skizzerz>	 you can make use of the supporting templates, it's not an official API but it'll be easier to parse
[15:23:55] <Bert_2>	 Skizzerz: supporting templates?
[15:24:18] <Skizzerz>	 Bert_2: https://www.mediawiki.org/wiki/Category:MediaWiki_version_information_templates
[15:24:32] <Bert_2>	 :O
[15:24:42] <Bert_2>	 that's exactly what I'm looking for :O
[15:25:18] <Bert_2>	 I presume items are removed whenever they are end-of-life?
[15:25:41] <Skizzerz>	 the templates themselves each have one bit of info, and the templates are edited with the current info whenever a new release happens
[15:26:16] <Bert_2>	 I think this is exactly what we need
[15:26:16] <Skizzerz>	 if you scroll down to "Pages in category" and click on, say, "Template:MW stable branch number" you can see what I mean
[15:26:19] <Bert_2>	 thank you very much :D
[15:26:24] <Bert_2>	 Skizzerz: I see
[15:27:36] <Bert_2>	 I better start scripting now :P
[15:28:04] <Skizzerz>	 hmm, it appears that those templates in turn use a lua module
[15:28:06] <Skizzerz>	 lemme dig deeper
[15:30:00] <Skizzerz>	 ok that module doesn't look easily parsable
[15:30:53] <Bert_2>	 oh, too bad
[15:30:56] <Bert_2>	 I like Lua :P
[15:31:27] <Skizzerz>	 just in case, https://www.mediawiki.org/wiki/Module:Version
[15:32:22] <Bert_2>	 and what's the relation between Template:MW ??? stable branch number and that Module?
[15:32:41] <Skizzerz>	 it doesn't track the .0 versions, whereas the EOL date is based on the release date of the .0
[15:32:50] <Skizzerz>	 the MW blah templates all invoke that module
[15:33:12] <Bert_2>	 well, if it's EOL it will be removed from the table and module
[15:33:16] <Bert_2>	 so that's fine for our purpose
[15:33:26] <Bert_2>	 not mentioned = you need to update
[15:36:06] <Skizzerz>	 yeah, just not useful for giving advanced warning about when support will end
[15:40:26] <Bert_2>	 yeah, we don't really do that
[15:40:40] <Bert_2>	 they already hate us for telling them not to run a drupal release from 2 years ago
[15:40:58] <Bert_2>	 which is of course insanely dangerous, but yeah, some people...
[19:40:04] <absor70>	 Does anyone know which method from CirrusSearch to use to send sort keys to an Elastic Doc?
[19:40:28] <absor70>	 I'm using ->sendData but receiving a msg saying that the page doesn't yet exist
[19:40:49] <absor70>	 which makes me think this method is only for updating existing sortkeys