From joe.kang at netex.com Wed Feb 4 13:21:50 2015 From: joe.kang at netex.com (Joseph Kang) Date: Wed, 4 Feb 2015 18:21:50 +0000 Subject: [Moin-user] Question about underlay pages in 1.9.3 Message-ID: Hi, all. I'm new to the list. Our company has been running an internal MoinMoin wiki for several years now but it wasn't actively maintained until recently. We recently went through a migration from 1.187 to 1.9.3. If anyone needs to know the specific versions I upgraded to in-between the start and end, I'd be happy to provide that info. The question I have is about the underlay pages that got installed with 1.9.3. I noticed that at some point, the markup for inserting a line break changed from [[BR]] to <
>. However the HelpOnFormatting page that got installed through the 1.9.3 LanguageSetup process shows that it's still [[BR]]. As far as I can tell, I am running with the underlay pages that were installed through 1.9.3. Is this the correct version of HelpOnFormatting for this release (mistakes and all)? I noticed that the layout and content on https://moinmo.in/HelpOnFormatting is completely different. I assume that's from the 1.9.8 version, correct? I cannot upgrade to 1.9.8 as our wiki is running on a major Linux distribution that, while current in other aspects, is only supporting Python 2.4 as the official, supported release. Thanks in advance! -Joseph K. -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul at boddie.org.uk Wed Feb 4 17:50:45 2015 From: paul at boddie.org.uk (Paul Boddie) Date: Wed, 4 Feb 2015 23:50:45 +0100 Subject: [Moin-user] Question about underlay pages in 1.9.3 In-Reply-To: References: Message-ID: <201502042350.46321.paul@boddie.org.uk> On Wednesday 4. February 2015 19.21.50 Joseph Kang wrote: > Hi, all. I'm new to the list. Our company has been running an internal > MoinMoin wiki for several years now but it wasn't actively maintained > until recently. We recently went through a migration from 1.187 to 1.9.3. > If anyone needs to know the specific versions I upgraded to in-between the > start and end, I'd be happy to provide that info. 1.187 sounds very old and not particularly Moin-like as a version number, but your problem description does seem to confirm that it's certainly an old, pre-1.6 version you're using. > The question I have is about the underlay pages that got installed with > 1.9.3. I noticed that at some point, the markup for inserting a line break > changed from [[BR]] to <
>. However the HelpOnFormatting page that got > installed through the 1.9.3 LanguageSetup process shows that it's still > [[BR]]. As far as I can tell, I am running with the underlay pages that > were installed through 1.9.3. Is this the correct version of > HelpOnFormatting for this release (mistakes and all)? I noticed that the > layout and content on https://moinmo.in/HelpOnFormatting is completely > different. I assume that's from the 1.9.8 version, correct? The markup changed with Moin 1.6, if I recall correctly, and the 1.9.3 pages should describe the modern markup. Maybe the old help pages have been cached, although I would have expected a "moin maint cleancache" to have been executed during an upgrade, depending on how the upgrade was done. > I cannot upgrade to 1.9.8 as our wiki is running on a major Linux > distribution that, while current in other aspects, is only supporting > Python 2.4 as the official, supported release. I would imagine that 1.9.3 with backported security fixes would be good enough, although the issue then is who is responsible for backporting those fixes. I imagine that the vendor doesn't provide the Moin package for 1.9.3 that you're intending to use (that is, you're using the source package from moinmo.in and not an OS vendor package) and thus isn't providing security updates for the code. Typically, the advice given out in such situations is to try and adopt a later Python version to be able to use a later Moin version, which for enterprise distributions like RHEL might involve additional semi-official repositories like EPEL. Otherwise, you'd need to maintain your own Python installation specifically for Moin, too, but you can at least do so in a confined part of the system and not try and replace the system Python, which is generally regarded as a bad thing to do. Paul From joe.kang at netex.com Wed Feb 4 18:39:44 2015 From: joe.kang at netex.com (Joseph Kang) Date: Wed, 4 Feb 2015 23:39:44 +0000 Subject: [Moin-user] Question about underlay pages in 1.9.3 In-Reply-To: <201502042350.46321.paul@boddie.org.uk> References: <201502042350.46321.paul@boddie.org.uk> Message-ID: Thanks for the reply, Paul. Your presumption is correct. I'm using the tar.gz distributions as downloaded from moinmo.in and I did perform a "moin maint cleancache" as part of the upgrade process. I happen to have a test machine that's a clone of the production system. I just deleted the underlay directory in my test wiki instance directory; copied /usr/share/moin/underlay into my wiki instance subdirectory; went through the process of installing the language packs all over again; and issued a "moin maint cleancache". The packs I chose were "all_system_pages", "all_help_pages", and "admin_pages". When I browse to this test instance and view the "HelpOnFormatting" page, it still shows the version that says the markup is "[[BR]]". I did some digging in the file system and noticed that the "/usr/share/moin//data/pages" subdirectory has the same directories that exists in "underlay" (with older file mod time/dates) in addition to the directories for our wiki's own content. I can only guess that it's pulling the outdated HelpOnFormatting page from there. As part of my upgrades, I always made sure I issued the "moin migration data" command. As far as I recall, I never saw any errors from them. Should the pages that are in "underlay" also exist in "data"? Or is that an artifact from running a really old version of MoinMoin and migrating it to newer versions? It may be helpful to provide the full list of versions I upgraded to/through: 1.187 (as shown on the page footer with "show_version=1" set in wikiconfig.py), 1.3.5, 1.5.3, 1.5.9, 1.6.0, and finally 1.9.3 Thanks again for your time and assistance. (Sorry about the top reply vs. inline. Stuck using Outlook.) -Joseph K. -----Original Message----- From: Paul Boddie [mailto:paul at boddie.org.uk] Sent: Wednesday, February 04, 2015 4:52 PM To: moin-user at lists.sourceforge.net Subject: Re: [Moin-user] Question about underlay pages in 1.9.3 On Wednesday 4. February 2015 19.21.50 Joseph Kang wrote: > Hi, all. I'm new to the list. Our company has been running an internal > MoinMoin wiki for several years now but it wasn't actively maintained > until recently. We recently went through a migration from 1.187 to 1.9.3. > If anyone needs to know the specific versions I upgraded to in-between > the start and end, I'd be happy to provide that info. 1.187 sounds very old and not particularly Moin-like as a version number, but your problem description does seem to confirm that it's certainly an old, pre-1.6 version you're using. > The question I have is about the underlay pages that got installed > with 1.9.3. I noticed that at some point, the markup for inserting a > line break changed from [[BR]] to <
>. However the HelpOnFormatting > page that got installed through the 1.9.3 LanguageSetup process shows > that it's still [[BR]]. As far as I can tell, I am running with the > underlay pages that were installed through 1.9.3. Is this the correct > version of HelpOnFormatting for this release (mistakes and all)? I > noticed that the layout and content on > https://moinmo.in/HelpOnFormatting is completely different. I assume that's from the 1.9.8 version, correct? The markup changed with Moin 1.6, if I recall correctly, and the 1.9.3 pages should describe the modern markup. Maybe the old help pages have been cached, although I would have expected a "moin maint cleancache" to have been executed during an upgrade, depending on how the upgrade was done. > I cannot upgrade to 1.9.8 as our wiki is running on a major Linux > distribution that, while current in other aspects, is only supporting > Python 2.4 as the official, supported release. I would imagine that 1.9.3 with backported security fixes would be good enough, although the issue then is who is responsible for backporting those fixes. I imagine that the vendor doesn't provide the Moin package for 1.9.3 that you're intending to use (that is, you're using the source package from moinmo.in and not an OS vendor package) and thus isn't providing security updates for the code. Typically, the advice given out in such situations is to try and adopt a later Python version to be able to use a later Moin version, which for enterprise distributions like RHEL might involve additional semi-official repositories like EPEL. Otherwise, you'd need to maintain your own Python installation specifically for Moin, too, but you can at least do so in a confined part of the system and not try and replace the system Python, which is generally regarded as a bad thing to do. Paul ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Moin-user mailing list Moin-user at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user From paul at boddie.org.uk Fri Feb 6 06:51:49 2015 From: paul at boddie.org.uk (Paul Boddie) Date: Fri, 6 Feb 2015 12:51:49 +0100 Subject: [Moin-user] Question about underlay pages in 1.9.3 In-Reply-To: References: <201502042350.46321.paul@boddie.org.uk> Message-ID: <201502061251.49796.paul@boddie.org.uk> On Thursday 5. February 2015 00.39.44 Joseph Kang wrote: > Thanks for the reply, Paul. Your presumption is correct. I'm using the > tar.gz distributions as downloaded from moinmo.in and I did perform a > "moin maint cleancache" as part of the upgrade process. Good. Sorry not to get back to you quickly about this, by the way! > I happen to have a test machine that's a clone of the production system. I > just deleted the underlay directory in my test wiki instance directory; > copied /usr/share/moin/underlay into my wiki instance subdirectory; went > through the process of installing the language packs all over again; and > issued a "moin maint cleancache". The packs I chose were > "all_system_pages", "all_help_pages", and "admin_pages". When I browse to > this test instance and view the "HelpOnFormatting" page, it still shows > the version that says the markup is "[[BR]]". > > I did some digging in the file system and noticed that the > "/usr/share/moin//data/pages" subdirectory has the same > directories that exists in "underlay" (with older file mod time/dates) in > addition to the directories for our wiki's own content. I can only guess > that it's pulling the outdated HelpOnFormatting page from there. As part > of my upgrades, I always made sure I issued the "moin migration data" > command. As far as I recall, I never saw any errors from them. I don't remember when the underlay system was introduced, but I think I first encountered it having already been using Moin for a while, so perhaps your old version didn't employ the underlay for help pages and had them all installed in the pages directory. I see that Moin 1.3 featured the underlay, at least: https://moinmo.in/MoinMoinRelease1.3 Why the pages didn't have their markup converted is a mystery to me, however. > Should the pages that are in "underlay" also exist in "data"? Or is that an > artifact from running a really old version of MoinMoin and migrating it to > newer versions? They only get replicated in the pages directory if they are edited, I think. > It may be helpful to provide the full list of versions I upgraded > to/through: 1.187 (as shown on the page footer with "show_version=1" set > in wikiconfig.py), 1.3.5, 1.5.3, 1.5.9, 1.6.0, and finally 1.9.3 > > Thanks again for your time and assistance. (Sorry about the top reply vs. > inline. Stuck using Outlook.) It's probably safe to try running without the duplicated help pages residing in the pages directory. Perhaps moving one of the page directories (pages/HelpOnFormatting, for example) out of the Moin installation to somewhere temporary, then possibly cleaning the Moin cache, and finally reloading the page in the browser might provide an insight into what is happening. Paul From joe.kang at netex.com Fri Feb 6 13:14:01 2015 From: joe.kang at netex.com (Joseph Kang) Date: Fri, 6 Feb 2015 18:14:01 +0000 Subject: [Moin-user] Question about underlay pages in 1.9.3 In-Reply-To: <201502061251.49796.paul@boddie.org.uk> References: <201502042350.46321.paul@boddie.org.uk> <201502061251.49796.paul@boddie.org.uk> Message-ID: No worries about the timeliness of your responses. While this is a problem, it's not a major or urgent one. I tried what you suggested and it worked! I got the updated HelpOnFormatting page out of the wiki when I moved the one that was in data/pages to /tmp, cleaned out the cache, and refreshed my browser page. Looks like I'll be doing some cleanup in data/pages on my test system and then in production. Thanks again. I'm going to consider this matter resolved at this point. Have a nice weekend! -Joe -----Original Message----- From: Paul Boddie [mailto:paul at boddie.org.uk] Sent: Friday, February 06, 2015 5:53 AM To: moin-user at lists.sourceforge.net Subject: Re: [Moin-user] Question about underlay pages in 1.9.3 On Thursday 5. February 2015 00.39.44 Joseph Kang wrote: > Thanks for the reply, Paul. Your presumption is correct. I'm using the > tar.gz distributions as downloaded from moinmo.in and I did perform a > "moin maint cleancache" as part of the upgrade process. Good. Sorry not to get back to you quickly about this, by the way! > I happen to have a test machine that's a clone of the production > system. I just deleted the underlay directory in my test wiki instance > directory; copied /usr/share/moin/underlay into my wiki instance > subdirectory; went through the process of installing the language > packs all over again; and issued a "moin maint cleancache". The packs > I chose were "all_system_pages", "all_help_pages", and "admin_pages". > When I browse to this test instance and view the "HelpOnFormatting" > page, it still shows the version that says the markup is "[[BR]]". > > I did some digging in the file system and noticed that the > "/usr/share/moin//data/pages" subdirectory has the same > directories that exists in "underlay" (with older file mod time/dates) > in addition to the directories for our wiki's own content. I can only > guess that it's pulling the outdated HelpOnFormatting page from there. > As part of my upgrades, I always made sure I issued the "moin migration data" > command. As far as I recall, I never saw any errors from them. I don't remember when the underlay system was introduced, but I think I first encountered it having already been using Moin for a while, so perhaps your old version didn't employ the underlay for help pages and had them all installed in the pages directory. I see that Moin 1.3 featured the underlay, at least: https://moinmo.in/MoinMoinRelease1.3 Why the pages didn't have their markup converted is a mystery to me, however. > Should the pages that are in "underlay" also exist in "data"? Or is > that an artifact from running a really old version of MoinMoin and > migrating it to newer versions? They only get replicated in the pages directory if they are edited, I think. > It may be helpful to provide the full list of versions I upgraded > to/through: 1.187 (as shown on the page footer with "show_version=1" > set in wikiconfig.py), 1.3.5, 1.5.3, 1.5.9, 1.6.0, and finally 1.9.3 > > Thanks again for your time and assistance. (Sorry about the top reply vs. > inline. Stuck using Outlook.) It's probably safe to try running without the duplicated help pages residing in the pages directory. Perhaps moving one of the page directories (pages/HelpOnFormatting, for example) out of the Moin installation to somewhere temporary, then possibly cleaning the Moin cache, and finally reloading the page in the browser might provide an insight into what is happening. Paul ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Moin-user mailing list Moin-user at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user From zenith158 at gmail.com Sat Feb 7 14:31:31 2015 From: zenith158 at gmail.com (Akshita Jha) Date: Sun, 8 Feb 2015 01:01:31 +0530 Subject: [Moin-user] Contributing to MoinMoin for GSOC 2015 Message-ID: Hi, I am an GSOC - 2015 Applicant. I am currently in my 3rd year B.Tech (Computer Science). I want to contribute to MoinMoin. I would be really grateful, if you could help me get started. -- Regards, Akshita Jha -------------- next part -------------- An HTML attachment was scrubbed... URL: From tw at waldmann-edv.de Mon Feb 9 05:33:33 2015 From: tw at waldmann-edv.de (Thomas Waldmann) Date: Mon, 09 Feb 2015 11:33:33 +0100 Subject: [Moin-user] Contributing to MoinMoin for GSOC 2015 In-Reply-To: References: Message-ID: <54D88CFD.20505@waldmann-edv.de> Hi Akshita, > I am an GSOC - 2015 Applicant. I am currently in my 3rd year B.Tech > (Computer Science). I want to contribute to MoinMoin. I would be really > grateful, if you could help me get started. Very likely most or all projects for GSOC will be based on moin 2.0 and we have a wiki page for that with all the important links, read it: https://moinmo.in/MoinMoin2.0 Also please join us on IRC #moin-dev on chat.freenode.net. Cheers, Thomas From kauer at biplane.com.au Sat Feb 14 22:10:26 2015 From: kauer at biplane.com.au (Karl Auer) Date: Sun, 15 Feb 2015 14:10:26 +1100 Subject: [Moin-user] Upgrading 1.8.1 to 1.9.8 Message-ID: <1423969826.29616.31.camel@karl> Hi all. I'm running a fairly old MoinMoin install - 1.8.1. An abridged version of SystemInfo is below. I've read the various upgrade HowTos and it *seems* straightforward. Does anyone have a recommended HowTo? I plan to try to install this on a Synology NAS eventually, but thought I would upgrade it first. Thanks, K. Python Version 2.5.1 (r251:54863, Jul 31 2008, 22:53:39) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] MoinMoin Version Release 1.8.1 [Revision release] [...] Global extension macros AbandonedPages, Action, AdvancedSearch, AttachInfo, AttachList, BR, EditTemplates, EditedSystemPages, EmbedObject, FootNote, FullSearch, FullSearchCached, GetText, GetText2, Hits, Include, InterWiki, LikePages, MonthCalendar, Navigation, NewPage, OrphanedPages, PageCount, PageHits, PageList, PageSize, RandomPage, RandomQuote, RecentChanges, ShowSmileys, StatsChart, SystemAdmin, SystemInfo, TableOfContents, TeudView, Verbatim, WantedPages, WikiConfig, WikiConfigHelp Local extension macros NONE Global extension actions AttachFile, DeletePage, Despam, LikePages, Load, LocalSiteMap, PackagePages, RenamePage, RenderAsDocbook, Save, SpellCheck, SubscribeUser, SyncPages, backup, bookmark, cache, chart, diff, dumpform, edit, fckdialog, fullsearch, info, links, login, logout, newaccount, newpage, pollsistersites, quicklink, quickunlink, recoverpass, refresh, revert, rss_rc, serveopenid, showtags, sisterpages, sitemap, subscribe, supplementation, thread_monitor, titleindex, unsubscribe, userprefs, userprofile Local extension actions NONE Global parsers text, text_cplusplus, text_creole, text_csv, text_diff, text_docbook, text_html, text_irssi, text_java, text_moin_wiki, text_pascal, text_python, text_rst, text_xslt Local extension parsers NONE Xapian search Disabled, Xapian and/or Python Xapian bindings not installed -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer at biplane.com.au) http://www.biplane.com.au/kauer http://twitter.com/kauer389 GPG fingerprint: 3C41 82BE A9E7 99A1 B931 5AE7 7638 0147 2C3C 2AC4 Old fingerprint: EC67 61E2 C2F6 EB55 884B E129 072B 0AF0 72AA 9882 From rohangoel0296 at gmail.com Mon Feb 16 12:35:13 2015 From: rohangoel0296 at gmail.com (Rohan Goel) Date: Mon, 16 Feb 2015 23:05:13 +0530 Subject: [Moin-user] GSoC 2015 Message-ID: Dear Developers, I am Rohan Goel , Computer Science undergraduate at BITS Pilani , India and am interested in working for your organization in GSoC 2015. As I am a beginner in open source coding , it would be great help if you guide me where to start from. My primary language of interest is Python. *Thanking You,* *Rohan Goel* *Under Graduate, B.E. (Hons) Computer Science Birla Institute of Technology and Science, Pilani* *K.K Birla Goa Campus* *+91 7722047225 **| rohangoel0296 at gmail.com * -------------- next part -------------- An HTML attachment was scrubbed... URL: From tw at waldmann-edv.de Fri Feb 20 16:25:58 2015 From: tw at waldmann-edv.de (Thomas Waldmann) Date: Fri, 20 Feb 2015 22:25:58 +0100 Subject: [Moin-user] Upgrading 1.8.1 to 1.9.8 In-Reply-To: <1423969826.29616.31.camel@karl> References: <1423969826.29616.31.camel@karl> Message-ID: <54E7A666.5080608@waldmann-edv.de> > I'm running a fairly old MoinMoin install - 1.8.1. An abridged version > of SystemInfo is below. > > I've read the various upgrade HowTos and it *seems* straightforward. > Does anyone have a recommended HowTo? docs/* in the download has instructions. > I plan to try to install this on a Synology NAS eventually, but thought > I would upgrade it first. Yeah, maybe try to get a newer python. 2.5.1 is too old these days. From tw at waldmann-edv.de Fri Feb 20 16:27:27 2015 From: tw at waldmann-edv.de (Thomas Waldmann) Date: Fri, 20 Feb 2015 22:27:27 +0100 Subject: [Moin-user] GSoC 2015 In-Reply-To: References: Message-ID: <54E7A6BF.4080205@waldmann-edv.de> > I am Rohan Goel , Computer Science undergraduate at BITS Pilani , India > and am interested in working for your organization in GSoC 2015. As I am > a beginner in open source coding , it would be great help if you guide > me where to start from. My primary language of interest is Python. https://moinmo.in/GoogleSoc2015 there are some links, read them. Also please join us on IRC, see there for details. From philip.colmer at linaro.org Tue Feb 24 10:51:37 2015 From: philip.colmer at linaro.org (Philip Colmer) Date: Tue, 24 Feb 2015 15:51:37 +0000 Subject: [Moin-user] Trying to understand notification behaviour in PageEdit.py Message-ID: I've got a nightly script that does a lot of automated changes to pages and I need to stop the notifications going out because of the email overhead it is generating. Looking at the code for PageEditor.py, I can see that saveText accepts the keyword notify: @keyword notify: if False (default: True), don't send a PageChangedEvent Indeed, there are calls to saveText within PageEditor.py where notify=False is set in the call. However, similarly changing my code so that it sets notify to False does not have the same effect. editor.saveText(text, 0, notify=False) still results in a notification being sent. What is *really* weird is that if I edit the saveText code so that the default value for notify is changed, thus: notify = kw.get('notify', False) I *still* get the notification when my script runs, but if I edit a page manually, NO notifications are sent. I've only got one file on my server called PageEditor.py so I am really bemused as to what the heck is going on here. I've trying adding logging to the code and, again, the logging only happens when I'm using moin via the web server. Nothing is output when my script runs. Any suggestions, please? Regards Philip -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.colmer at linaro.org Tue Feb 24 10:53:19 2015 From: philip.colmer at linaro.org (Philip Colmer) Date: Tue, 24 Feb 2015 15:53:19 +0000 Subject: [Moin-user] Programmatic creating/editing of pages In-Reply-To: References: <54B3CEB8.1080003@waldmann-edv.de> Message-ID: > IIRC there is a parameter of PageEditor (or the save call) where you can > switch off revisioning. There is - finally got back to looking at this today. It is a parameter of PageEditor: editor = PageEditor(request, 'Internal/meet-the-team', do_revision_backup=False) Regards Philip On 12 January 2015 at 18:10, wrote: > If I want to create a dynamic page in the wiki, I just use a macro which > links the page to externally generated data. > > e.g. We have a dynamic list of machines, updated each time DHCP runs. > The DHCP server updates a database, the macro queries that database. > > You could do the same with your pictures, just store then in a database as > blobs. > > The wiki page says just (as wiki text) > > -------- > {{{#!wiki comment/dashed > Latest Data from DHCP /usr/local/share/moin/data/plugin/macro/QueryDB.py > Data is collected by avldns0 and put into a MySQL Database, MACLookup > }}} > > '''Last Query : <>''' > <> > --------- > > The QueryDB and Now functions generate HTML > > > > > From: Thomas Waldmann > To: moin-user at lists.sourceforge.net, > Date: 12/01/2015 15:05 > Subject: Re: [Moin-user] Programmatic creating/editing of pages > ------------------------------ > > > > > 1. I'd prefer NOT to have page history for these pages. It takes up disc > > space and isn't really necessary. > > IIRC there is a parameter of PageEditor (or the save call) where you can > switch off revisioning. > > > 2. I'd prefer NOT to have changes to these pages show up in the > > RecentChanges list. The reason for this request is because part of the > > update process requires me to update the photos for each person. Since I > > can't (easily) do a file comparison to see if the photo has changed, I > > replace all of the photos anyway just to be on the safe side. > > I don't think you can do this easily using the existing API. > > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > vanity: www.gigenet.com > _______________________________________________ > Moin-user mailing list > *Moin-user at lists.sourceforge.net* > *https://lists.sourceforge.net/lists/listinfo/moin-user* > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > www.gigenet.com > _______________________________________________ > Moin-user mailing list > Moin-user at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/moin-user > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.colmer at linaro.org Wed Feb 25 05:02:13 2015 From: philip.colmer at linaro.org (Philip Colmer) Date: Wed, 25 Feb 2015 10:02:13 +0000 Subject: [Moin-user] Trying to understand notification behaviour in PageEdit.py Message-ID: I've got a nightly script that does a lot of automated changes to pages and I need to stop the notifications going out because of the email overhead it is generating. Looking at the code for PageEditor.py, I can see that saveText accepts the keyword notify: @keyword notify: if False (default: True), don't send a PageChangedEvent Indeed, there are calls to saveText within PageEditor.py where notify=False is set in the call. However, similarly changing my code so that it sets notify to False does not have the same effect. editor.saveText(text, 0, notify=False) still results in a notification being sent. What is *really* weird is that if I edit the saveText code so that the default value for notify is changed, thus: notify = kw.get('notify', False) I *still* get the notification when my script runs, but if I edit a page manually, NO notifications are sent. I've only got one file on my server called PageEditor.py so I am really bemused as to what the heck is going on here. I've trying adding logging to the code and, again, the logging only happens when I'm using moin via the web server. Nothing is output when my script runs. Any suggestions, please? Regards Philip