[03:45:02] RainbowSprinkles: i am disappoint [09:02:30] Hi all, what is the recommended way to generate pdf for a single page entry in mediawiki? (deployed in linux/ubuntu server) - thanks [09:56:39] phiofx: Print it it browser to PDF. [11:06:24] tale: yes, thanks tale, this is an option but I wonder how consistent is the output for the users (will all the different browsers / mobile etc.)... any experiences? [11:07:48] Hi [13:47:40] hello, what's the best way to mirror mediawiki? (non wikipedia-mediawiki that is) [16:07:05] antiglare: mirror you mean create duplicate instance? what database are you using. its quite easy with sqlite. you just copy db and php files to new server and you are done. [16:16:27] if i have pages like docs/topic/1.0/page1, docs/topic/1.0/page2, docs/topic/2.0/page1, docs/topic/1.0/page2 - can i have a template with links that lead to the same page, but different version ? [16:16:42] for example, link "2.0" on docs/topic/1.0/page1 would lead to docs/topic/2.0/page1 [16:16:56] same link on docs/topic/1.0/page2 would lead to docs/topic/2.0/page2 [16:17:15] (in the initial list the last one has the wrong version :) ) [16:21:16] Richlv: yes, it should be doable. MediaWiki supports relative links like [[../2.0/page1]] [16:24:18] Vulpix, oh, that sounds wonderful - thought of it, but didn't expect it to work. will test, thank you :) [16:25:45] you can play with {{SUBPAGENAME}} on the template, like [[../{{{1}}}/{{SUBPAGENAME}}]] [16:27:27] Vulpix, looks like a great start, thank you again [16:36:01] hello, i have a question: if, i have a wiki with multiple languages but pages between languages does not necessarily have to be translations, it's better to create a wiki farm, or may be better to use the translate extension (to keep it simple) , and use the interwiki extension to link between translation pages with the $url/$1/$lang pattern? [16:39:17] the translate extension works only when all languages are translations (it works paragraph by paragraph [16:39:50] you can still have languages as subpages, but don't use the translate extension [16:45:54] phiofx: There's a 'Download as PDF' option in the left sidebar. [16:47:40] Vulpix: how shall i organize languages as subpages? [16:48:43] SirLouen: maybe the Polyglot extension is more for you [16:48:59] (if it still works - i don't think i touched it since i wrote it 10 years ago) [16:49:29] SirLouen: the convention is to use Blabla/en, Blabla/fr, Blabla/ru, etc [16:49:44] (for both, Translate and Polyglot) [16:49:52] yes, I found so with the translate extension [16:51:26] that i could use the $1/$lang for interwiki links, the problem is that as Vulpix suggests, with the translate extension I can only translate paragraph by paragraph, so for example if the main page has 10 p and the second language has 20 then i will have issues [16:52:46] i'm going to checkout the polyglot extension it seems to have some commits in the last months [16:52:55] you can still use the title/lang subpage scheme, with interwikis, and without using the translate extension [16:54:09] using subpages or a wiki family depends on how large the wiki will be [16:54:20] SirLouen: Polyglot does these "interwiki links" automatically [16:54:28] that's exactly the idea of that extension. [16:54:47] find subpages that correspond to language codes, list them in the sidebar as language links [16:55:36] i see, it looks pretty awesome for this purpose [16:55:54] and only needs 1 wiki install i suppose [16:56:05] not like the wiki language farm idea [16:56:26] that i think it could be an overkill for my project [16:58:55] Niharika: thanks, I think this probably the PdfExport extension they use at mediawiki.org, but if you read through the extension docs there are many options for backends and it seems the whole approach is being abandoned in favor of the "electron service". Its not clear what to do in the short-mid term [17:02:41] phiofx: Yeah, I was reading through the docs just now. I feel like for your use case that extension might suffice (if you can get it to work) because it appears to me the reason they are switching is performance concerns. There is also an external tool for creating PDFs apparently: http://mediawiki2latex.wmflabs.org [17:04:51] Niharika: performance should not be problem at this point 8-), I guess I will try some of the backends to see how they work. Hopefully they are listed in order of preference :-) [17:25:27] phiofx, the original one is using mariadb, with mirror, i meant creating wikis which would mirror each others contents , lets call original A and new one B, say after initial copying of the db from A, B is changed, is there anyway to synchronize A with B, and keep those synchronized other than copying db back and forth [17:50:29] antiglare: no. this is called "fork and merge" logic. it has been discussed many times, but mediawiki does not support it, at all. [18:06:54] DanielK_WMDE: i've been reading about polyglot, the main problem is how to fix the template texts. It used to be done with multilang but now it's deprecated so i can't find an easy fix [18:24:28] thank you DanielK_WMDE [19:49:20] Richlv: yes, it should be doable. MediaWiki supports relative links like [[../2.0/page1]] [19:49:39] testing this suggestion, but that does not create links. just plaintext represntation with square brackets as-is [19:50:30] Esther: for sure :-) [19:51:51] there was https://www.mediawiki.org/w/index.php?oldid=2514700 , but that's archived [19:52:07] https://www.mediawiki.org/wiki/Help:Links#External_links_to_internal_pages mentions subpage links, but that's different [19:52:10] I'm trying to create a Wiki with multiple language Pages (and the same page can have multiple langs not necessarily translations). The wiki is not going to be too big. Which is the solution your prefer the most? [20:04:11] Vulpix, heya, sorry to bother you - but your relative link suggestion does not work for me, getting plaintext when using something like [[../2.0/page1]] [20:06:13] Remove .. just /2.0/page1 [20:06:23] Surrounded in [] [20:06:27] X2 [20:08:28] Zppix: http://test.wikidex.net/wiki/Usuario:Ciencia_Al_Poder/Pruebas/Test2 [20:09:07] The page isnt existant [20:09:16] Create a page there and it will be blue [20:09:22] yes but the link is working [20:09:30] Correct [20:09:50] Zppix, doesn't that require explicitly enabling subpages that are disabled by default ? [20:09:59] No [20:10:07] Yes [20:10:10] yes, it requires subpages to be enabled [20:10:18] Yes it does i misread [20:10:37] some namespaces have them enabled by default IIRC [20:10:50] Vulpix: yes [20:10:59] https://www.mediawiki.org/wiki/Manual:$wgNamespacesWithSubpages [20:11:09] just not the main namespace [20:11:17] yeah, was reading that page earlier [20:11:18] eh [20:11:30] will try to convince somebody to enable them then :) [20:11:32] thanks again [20:12:01] yw :) [20:12:08] hi, I'm trying to fix a script that uses API to create new user accounts in a mediawiki instance; it used to work until we upgraded to MW 1.29; the script uses https://github.com/alexz-enwp/wikitools [20:12:26] are there any known issues in MW and/or wikitools or elsewhere that might cause these issues? [20:12:42] it seems I'm getting the "notoken" error, but it's unclear why [20:13:40] in the 1.29 changelog I've seen "Submitting sensitive authentication request parameters to action=login, action=clientlogin, action=createaccount, action=linkaccount, and action=changeauthenticationdata in the query string is now an error. They should be submitted in the POST body instead." [20:13:59] is it possible that this is causing the problem and/or that wikitools 1.3 doesn't support this yet? [20:16:43] https://www.mediawiki.org/wiki/API:Client_code/Evaluations/wikitools mentions wikitools so I'm assuming it's officially supported and kept up-to-date with MW API changes? [20:28:16] hooray, got the subpage functionality enabled, and ../stuff now works [20:28:23] Vulpix, thanks again :) [20:28:35] :) [20:32:16] hmm, the [[../{{{1}}}/{{SUBPAGENAME}}]] part i cannot get working, though [20:37:46] why not? [20:51:43] uwe_: wikitools is not a WMF project as far as I can tell, and as such is not "officially" supported [20:52:22] you can try opening an issue on that github link you gave. [20:53:47] ok, thx [20:54:05] is there any other more actively maintained or more officially supported python API project? [20:55:04] uwe_: what exactly are you needing an api project for? [20:58:16] we're using a script to semi-automatically create user accounts in a custom mediawiki install [21:09:05] Vulpix, not sure what should {{{1}}} resolve to in this case, it did not resolve for me. this worked (but a bit ugly) : [[{{#titleparts: {{PAGENAME}}|-2}}/2.0/{{SUBPAGENAME}}|2.0]] [21:10:09] Richlv: I expected your template to be used as {{TEMPLATENAME|2.0}}, so {{{1}}} becomes 2.0 when transcluded [21:16:49] Vulpix, yaaaaaay. that indeed works, yet another hardcoded thing goes away. i still ended up parsing with titleparts, but looks like it all can be a single template now [21:19:01] Can someone please direct me to documentation at mediawiki.com regarding how to create a form on a page? All I'm finding is deprecated extensions. Thank you [21:20:08] Amie: a form for editing a page? [21:37:24] Vulpix, no, a form to gather information from a user. It is for ordering something from the site. Is that possible? [21:39:20] I don't think so... use an external service? [21:39:46] You could use contactpage ext i guess [21:41:25] I'll check out the contactpage extension and see if that works. Thanks for your help.