From Christian.Molecki at stala.bwl.de Thu Feb 1 02:43:47 2018 From: Christian.Molecki at stala.bwl.de (Molecki, Christian (STL)) Date: Thu, 1 Feb 2018 07:43:47 +0000 Subject: [moin-user] external link prefix Message-ID: <205F109FB2535542BD9DB0753EFF6D3326E70572@BWLSM15.ZD.BWL.NET> Hello everyone, is it possible to configure MoinMoin to handle a external http(s) link like prefix:http(s)://foo.com ? In our environment its only allow to open external links in a certain browser. The urls are opened directly in this browser with a specific prefix. http://google.com -> Firefox, Internet Explorer... prefix:http://google.com -> "External Browser" Mit freundlichen Gr??en Christian Molecki -------------------------------------------- Statistisches Landesamt Baden-W?rttemberg Referat 14: Systemtechnik und Datenmanagement OE 143: Systemtechnik, Gro?rechner, Internettechnik, Datenmanagement B?blinger Str. 68 70199 Stuttgart Tel.: 0711/641-2457 Fax: 0711/641-2440 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rog7993 at web.de Thu Feb 8 09:34:37 2018 From: rog7993 at web.de (rog7993 at web.de) Date: Thu, 8 Feb 2018 15:34:37 +0100 Subject: [moin-user] =?utf-8?b?fHw8dGFibGVjbGFzcz0i4oCmIj4gcHJvY2Vzc2lu?= =?utf-8?q?g_broken_in_Moin_1=2E9=2E9?= Message-ID: Hello, I've just upgraded to MoinMoin 1.9.9 and stumbled upon this bug. What is the recommend workaround at the moment? Replacing werkzeug 0.11.11 against version 0.8.3, which was delivered with MoinMoin 1.9.8. I've tried this and it seems to work. But I'm not sure, whether this have unwanted side effects. Are there better solutions? Regards, Ingo From paul at boddie.org.uk Thu Feb 8 10:20:29 2018 From: paul at boddie.org.uk (Paul Boddie) Date: Thu, 8 Feb 2018 16:20:29 +0100 Subject: [moin-user] || processing broken in Moin 1.9.9 In-Reply-To: References: Message-ID: <201802081620.29770.paul@boddie.org.uk> On Thursday 8. February 2018 15.34.37 rog7993 at web.de wrote: > > I've just upgraded to MoinMoin 1.9.9 and stumbled upon this bug. What is > the recommend workaround at the moment? Replacing werkzeug 0.11.11 > against version 0.8.3, which was delivered with MoinMoin 1.9.8. I've > tried this and it seems to work. But I'm not sure, whether this have > unwanted side effects. > > Are there better solutions? I did provide a patch to the moin-devel mailing list that seems to fix the regression. That might be a better alternative. https://mail.python.org/pipermail/moin-devel/2017-December/001887.html I cannot say what benefits the newer version of werkzeug provides, although one can always assume that bugs were fixed (as well as being introduced) and that the newer version is worth having purely on that basis. Paul From rog7993 at web.de Thu Feb 8 13:12:23 2018 From: rog7993 at web.de (rog7993 at web.de) Date: Thu, 8 Feb 2018 19:12:23 +0100 Subject: [moin-user] =?utf-8?b?fHw8dGFibGVjbGFzcz0i4oCmIj4gcHJvY2Vzc2lu?= =?utf-8?q?g_broken_in_Moin_1=2E9=2E9?= In-Reply-To: <201802081620.29770.paul@boddie.org.uk> References: <201802081620.29770.paul@boddie.org.uk> Message-ID: Hello Paul, Am 08.02.2018 um 16:20 schrieb Paul Boddie: > On Thursday 8. February 2018 15.34.37 rog7993 at web.de wrote: >> >> I've just upgraded to MoinMoin 1.9.9 and stumbled upon this bug. What is >> the recommend workaround at the moment? Replacing werkzeug 0.11.11 >> against version 0.8.3, which was delivered with MoinMoin 1.9.8. I've >> tried this and it seems to work. But I'm not sure, whether this have >> unwanted side effects. >> >> Are there better solutions? > > I did provide a patch to the moin-devel mailing list that seems to fix the > regression. That might be a better alternative. > > https://mail.python.org/pipermail/moin-devel/2017-December/001887.html Thank you. The patch seems to work for me. The patch is shown somewhat crippled on the mailing list web archive. I wondered about this: - expected = r'' + expected = r'' After looking in the file I understood the meaning. Probably the first line should look like this: - expected = r'<tablewidth="80">' I assume, your original post on the mailing list was correct. Regards, Ingo From paul at boddie.org.uk Thu Feb 8 15:00:54 2018 From: paul at boddie.org.uk (Paul Boddie) Date: Thu, 8 Feb 2018 21:00:54 +0100 Subject: [moin-user] || processing broken in Moin 1.9.9 In-Reply-To: References: <201802081620.29770.paul@boddie.org.uk> Message-ID: <201802082100.55305.paul@boddie.org.uk> On Thursday 8. February 2018 19.12.23 rog7993 at web.de wrote: > > Am 08.02.2018 um 16:20 schrieb Paul Boddie: > > > > https://mail.python.org/pipermail/moin-devel/2017-December/001887.html > > Thank you. The patch seems to work for me. Great! > The patch is shown somewhat crippled on the mailing list web archive. I > wondered about this: > > - expected = r'' > + expected = r'' > > After looking in the file I understood the meaning. Probably the first > line should look like this: > > - expected = r'<tablewidth="80">' > > I assume, your original post on the mailing list was correct. Yes, I suppose this is a fault with the mail archiving software. In fact, the page source looks like this: - expected = r'<tablewidth="80">' + expected = r'<tablewidth="80">' Obviously, this isn't correct, either. It should be... - expected = r'<tablewidth="80">' + expected = r'<tablewidth="80">' However, this is part of a test in the test suite, so it will just mean that the test will fail. The functionality will still be correct in Moin itself. Apologies to people reading this in the Web archive where the above extracts will probably all appear identical and/or wrong. Paul From dawn.messerly at knockinc.com Mon Feb 26 15:48:45 2018 From: dawn.messerly at knockinc.com (Dawn Messerly) Date: Mon, 26 Feb 2018 14:48:45 -0600 Subject: [moin-user] Where to add analytics embed code for tracking page views on every page of our wiki? Message-ID: <727834D9-30D2-464F-AEFB-FF2B65585F4A@knockinc.com> Hello, If we wanted to add analytics tracking for page views on every page of our wiki, what would be the best place to add that embed code so that it will not be blown away by a moinmoin update? We had embed code in the footer prior to our update from 1.9.8 to 1.9.9, but the update appears to have blown it away and we don?t want to risk that happening again for a future update. FWIW we are using Piwik for analytics. Thank you! Dawn -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4079 bytes Desc: not available URL: From paul at boddie.org.uk Mon Feb 26 17:31:33 2018 From: paul at boddie.org.uk (Paul Boddie) Date: Mon, 26 Feb 2018 23:31:33 +0100 Subject: [moin-user] Where to add analytics embed code for tracking page views on every page of our wiki? In-Reply-To: <727834D9-30D2-464F-AEFB-FF2B65585F4A@knockinc.com> References: <727834D9-30D2-464F-AEFB-FF2B65585F4A@knockinc.com> Message-ID: <201802262331.34162.paul@boddie.org.uk> On Monday 26. February 2018 21.48.45 Dawn Messerly wrote: > > If we wanted to add analytics tracking for page views on every page of our > wiki, what would be the best place to add that embed code so that it will > not be blown away by a moinmoin update? It depends who is doing the updating. I guess you're referring to the normal migration script as opposed to any software distribution package update (which might do its own helpful stuff). > We had embed code in the footer prior to our update from 1.9.8 to 1.9.9, > but the update appears to have blown it away and we don?t want to risk > that happening again for a future update. Note that recent discussion found other issues with 1.9.9 (that table formatting problem), making me rather suspicious that we will find other interesting problems at some point. It surprises me that the migration script would touch what is effectively a configuration setting, though. > FWIW we are using Piwik for analytics. I'm pretty sure that in a similar situation, the HTML footer region was used to deploy Piwik's JavaScript successfully. Interestingly, a related discussion was then had about deploying analytics tools where legislation requires notices and opt-outs, so be sure to follow the recommended practices, as I'm sure you are already doing. :-) Paul