[01:46:42] hey is mediawiki participating in GoC this year? [01:47:23] google summer of code, sorry messed up the acronym [06:50:21] Hi. I'm trying to use TemplateStyles. The script I'm trying to use says that I need the css file to be "Sanitized CSS". But when I change the model of the page to that, I get a fatal error. [07:02:29] https://www.mediawiki.org/wiki/Topic:Ukv6pdo96a8qfur2 [07:02:42] That seems to be the problem but I don't see a solution. I'm not using Git/Composer. [07:14:36] I guess I am missing Wikimedia\CSS\Parser\Parser. Can anyone tell me where to find that? [08:26:46] Grobbs: how did you download TemplateStyles? [08:27:59] hm, I think there's a bug with the extension distributor [10:25:36] Hey guys, just wondering if there are any recommended and simple templates to get started in mediawiki? I've been trying to figure out how to install stuff like InfoBoxes but just having some trouble [10:48:12] Grobbs: if you have shell access to the server you can probably just run 'composer update' in the MediaWiki root directory to get the necessary files [10:49:32] Guest44978: infoboxes tend to be the opposite of simple [11:04:59] Thanks for that @tgr, I'm not sure if I have shell access or not, I'll have to check [11:06:20] you can run it on your own machine and upload the result if you really have to [11:07:04] in theory Special:ExtensionDistributor should do all that so you don't have to, but apparently something went wrong with that [11:07:43] Ah I see, are there any known extension that handle stuff like that? [11:18:00] yeah, that's the extension that serves tarball downloads on mediawiki.org [11:18:16] so if you are not using git, you probably got the code via that [15:00:17] Bored? Call the official freenode IRC partyline at +4521137886 [15:00:23] Bored? Call the official freenode IRC partyline at +4521137886 [15:02:31] Bored? Call the official freenode IRC partyline at +4521137886 [15:02:54] Wow. I wonder if there is actually someone at that phone number [15:04:20] £0.091/minute to call it on skype [15:04:52] Oh, yes, you have to pay for calls to POTS systems. How quaint. [15:05:20] Should ask them for a sip uri [15:42:49] I'm trying to parse data off of pages. parsing the html is icky. is there a way I can get the data as json or xml or something? like this page: [15:42:51] https://www.mediawiki.org/wiki/EMWCon_Spring_2019/Update_on_Some_Internal_Government_Wikis [15:43:27] CarlFK, https://www.mediawiki.org/wiki/API:Main_page [15:44:21] or more specifically, https://www.mediawiki.org/wiki/API:Parsing_wikitext [15:46:58] andre__: perfect - thanks [16:43:17] In TWiki we can create pages with a "template", which is a bit like default content for a new page that a user can choose to replace any part of [16:43:38] Is there a similar mechanism, perhaps using an extension, that I can use to achieve the same thing in MediaWiki? [16:44:27] !editintro [16:44:35] hmm, guess that's the wrong macro [16:45:02] I've found https://www.mediawiki.org/wiki/Extension:Create_Page which seems to be able to do such a thing up to a point, but I'd rather not have to put a page together to link to all the "templates" / scaffolds [16:45:51] bootc: So the main way people usually do this is with the https://www.mediawiki.org/wiki/Extension:InputBox and the preload parameter [16:46:00] The extension isn't neccesary, it just provides a UI for it [16:46:19] you can also just manually create a link with preload url parameter - https://www.mediawiki.org/wiki/Manual:Creating_pages_with_preloaded_text [16:46:31] the preload url parameter points to a page that is used as the default content for the new page [16:47:05] You can also use the editintro parameter to provide instructions separate from the default contents [16:54:41] bawolff: thanks, that's really helpful [16:55:23] can I preload the contents from an existing page, perhaps even a template? [16:57:53] bawolff: oh the preload functionality expects exactly that, brilliant [16:58:00] many thanks indeed [21:18:49] I use the api to get wikitext from https://www.mediawiki.org/wiki/EMWCon_Spring_2019/Transitioning_an_Existing_Wiki_to_Incorporate_Structured_Data [21:19:17] Examples will be given using both [[Extension:Semantic MediaWiki|Semantic MediaWiki]] [21:19:43] this is going to be copied to youtube's description. [21:20:15] I can live with just pushing the markup, (md?) but if the wiki engine will give me URLs that might be better [21:24:32] The wikimarkup is not md format [21:25:05] you can get it at https://www.mediawiki.org/w/index.php?title=EMWCon_Spring_2019/Transitioning_an_Existing_Wiki_to_Incorporate_Structured_Data&action=raw [21:28:07] CarlFK: Some people also find it easier to screen scrap from https://www.mediawiki.org/api/rest_v1/page/html/EMWCon%20Spring%202019%2FTransitioning%20an%20Existing%20Wiki%20to%20Incorporate%20Structured%20Data [21:28:12] which has different html formatting [21:31:30] I've got code to get the =raw version: https://github.com/CarlFK/veyepar/blob/master/dj/scripts/addeps.py#L4275-L4290 [21:32:27] the "easier to screen scrap" version is kinda what I want, but I would need to fix the URLs to include the http://host... [21:33:19] I'm not surprised what I want doesn't exist. it is borderline rude to copy text to some other site [21:33:20] https://www.mediawiki.org/w/index.php?title=EMWCon_Spring_2019/Transitioning_an_Existing_Wiki_to_Incorporate_Structured_Data&action=render also exists, it uses the normal html, but no UI stuff and urls are absolute [21:33:40] This is wiki though. Sharing is caring! [21:33:58] action=render oh neat [21:34:13] and yes. [21:34:24] Its primarily used for when mediawiki internally needs to copy things around (Like image descriptions from commons) [21:41:41] damm. I want action=render but for the json [21:42:37] at this point I'm more having fun than getting real work done, and I'm running out of time [21:46:34] href="//www.mediawiki.org/wiki/Extension:Cargo" is the // there valid? [21:46:42] view-source:https://www.mediawiki.org/w/index.php?title=EMWCon_Spring_2019/Transitioning_an_Existing_Wiki_to_Incorporate_Structured_Data&action=render [21:47:07] / means protocol relative [21:47:11] // means protocol relative [21:50:58] neat. that was my guess, never saw it before [21:58:42] Hmm, we could probably kill protocol-relative links by now [22:00:42] Death to plain http! [22:01:03] protocol relative combined with HSTS is an interesting combo, logically speaking [23:40:51] but protocol relative links are so pretty [23:41:41] Won't anyone think of the 6 bytes!