From p.f.moore at gmail.com Fri Dec 2 15:45:35 2011 From: p.f.moore at gmail.com (Paul Moore) Date: Fri, 2 Dec 2011 20:45:35 +0000 Subject: [Moin-user] Caching generated content from a parser Message-ID: I'm writing a parser which generates content (an image) based on the text provided to the parser - something like the Google Chart or Graphviz parsers. I'm trying to decide where would be the best place to store the generated content. The Google Chart parser uses the cache, which feels like the best option to me. (The Graphviz parser's use of attachments feels like it exposes too many of the gory details to the user for me). It's easy to write the code to cache the image: def format(self, formatter): key = cache.key(...) if not cache.exists(self.request, key): # Generate data cache.put(self.request, key=key, data=data, filename="image.png") self.request.write(formatter.image(src=cache.url(self.request, key))) At the moment, I generate the key using self.raw (the raw data from the formatter) but that means that every time the data changes, a new cache entry is created and the old one is never removed. What would be *much* better would be if I could generate a unique ID for each region on the page using my formatter, then I could regenerate the *same* cache entry when the data changed. Is that possible? Can a formatter see its context like this? (I seem to recall once seeing some code that set a counter on the request object, but I can't get anything like that to work...) Outside of the "pure" parser activities, I have some housekeeping concerns. A very active wiki could end up generating lots of images, and while disk is cheap, image files are larger than text files, and I'd like some means of keeping disk usage reasonable. There are two aspects to this: 1. I don't know enough about the MoinMoin caching system to know when caches are cleared, and how. Are page-level cached items cleared when the page cache is cleared? (If so, that's a point against using the cache action, as that uses a wiki-level cache). 2. I don't quite know *when* I would age cache entries out yet, but my instincts say that when a new version of the page is created would be a reasonable time. Ideally, I'd check at that stage what images are cached for the page, and delete any that related to an older version of the page and hadn't been used "recently". (Getting the details right might be fiddly, but that's the general idea). Is there a way of setting some code to run when a new version of a page is created like this? (And if so, is it possible to associate it with the formatter somehow, so that it only runs for pages using my formatter?) Pointers to documentation would be great - as would suggestions as to how to find my way through the relevant bits of the source. Thanks, Paul PS I have a feeling all of this would be much easier in Moin 2, with its mimetype items, but I get the feeling that Moin 2 is still a reasonable way away from being ready for production use, so I think I have to stick with 1.9 for this :-( From paul at boddie.org.uk Fri Dec 2 18:18:29 2011 From: paul at boddie.org.uk (Paul Boddie) Date: Sat, 3 Dec 2011 00:18:29 +0100 Subject: [Moin-user] Caching generated content from a parser In-Reply-To: References: Message-ID: <201112030018.29395.paul@boddie.org.uk> On Friday 02 December 2011 21:45:35 Paul Moore wrote: > I'm writing a parser which generates content (an image) based on the > text provided to the parser - something like the Google Chart or > Graphviz parsers. I'm trying to decide where would be the best place > to store the generated content. The Google Chart parser uses the > cache, which feels like the best option to me. (The Graphviz parser's > use of attachments feels like it exposes too many of the gory details > to the user for me). This is precisely the dilemma I had recently: I was/am writing a chart data parser that uses SVG as output. I've chosen to go with attachments, however, just like the Graphviz parser (the simpler one of the two, at least) because the caching behaviour was driving me up the wall, whereas you can always delete attachments manually and guarantee that the parser will regenerate the output. Another benefit is that if you ever need to export the page, it might be sufficient to just write a script to grab the page and attachments. Paul From tw-public at gmx.de Fri Dec 2 22:07:27 2011 From: tw-public at gmx.de (Thomas Waldmann) Date: Sat, 03 Dec 2011 04:07:27 +0100 Subject: [Moin-user] Caching generated content from a parser In-Reply-To: References: Message-ID: <1322881647.22700.4.camel@x300.localdomain> >At the moment, I generate the key using self.raw (the raw data from > the formatter) but that means that every time the data changes, a new > cache entry is created and the old one is never removed. Well, if one needs to reclaim the disk space, one could just kill all the caches. Caches should not be authoritative, so they will rebuild then automatically. Although this is not super-clean, it is maybe much simpler than implementing some complex thing to manage this. Especially considering that moin2 might be very different then. > PS I have a feeling all of this would be much easier in Moin 2, with > its mimetype items, but I get the feeling that Moin 2 is still a > reasonable way away from being ready for production use, so I think I > have to stick with 1.9 for this :-( Yes, if you need it in production mode quickly, use 1.9. See also the hints about that on the MoinMoin2.0 wiki page. From p.f.moore at gmail.com Sat Dec 3 06:33:59 2011 From: p.f.moore at gmail.com (Paul Moore) Date: Sat, 3 Dec 2011 11:33:59 +0000 Subject: [Moin-user] Caching generated content from a parser In-Reply-To: <1322881647.22700.4.camel@x300.localdomain> References: <1322881647.22700.4.camel@x300.localdomain> Message-ID: On 3 December 2011 03:07, Thomas Waldmann wrote: >>At the moment, I generate the key using self.raw (the raw data from >> the formatter) but that means that every time the data changes, a new >> cache entry is created and the old one is never removed. > > Well, if one needs to reclaim the disk space, one could just kill all > the caches. Caches should not be authoritative, so they will rebuild > then automatically. > > Although this is not super-clean, it is maybe much simpler than > implementing some complex thing to manage this. Especially considering > that moin2 might be very different then. Good point. The only (remaining) issue is that I don't think I can easily locate all the cached values relating to my formatter. Rethinking this, I might go with the attachment approach as suggested by Paul Boddie. Or maybe just stop worrying about it for now and see if it's actually a real problem. The one thing I *would* like to know, though, is whether there is a way for a formatter to obtain a unique identifier for the region it's responsible for (page ID plus occurrence ID, something like that). Having that would mean I could write fairly naive code without falling into the trap of having something that fails when there are 2 occurrences on the same page. >> PS I have a feeling all of this would be much easier in Moin 2, with >> its mimetype items, but I get the feeling that Moin 2 is still a >> reasonable way away from being ready for production use, so I think I >> have to stick with 1.9 for this :-( > > Yes, if you need it in production mode quickly, use 1.9. > See also the hints about that on the MoinMoin2.0 wiki page. It looks great - is "maybe end of 2011" still "not totally unrealistic"? If it's that close, then I might be tempted to have a play with it even if it's not something I can use in production yet... Paul. From p.f.moore at gmail.com Sat Dec 3 10:33:28 2011 From: p.f.moore at gmail.com (Paul Moore) Date: Sat, 3 Dec 2011 15:33:28 +0000 Subject: [Moin-user] Caching generated content from a parser In-Reply-To: References: <1322881647.22700.4.camel@x300.localdomain> Message-ID: On 3 December 2011 11:33, Paul Moore wrote: > The one thing I *would* like to know, though, is whether there is a > way for a formatter to obtain a unique identifier for the region it's > responsible for (page ID plus occurrence ID, something like that). > Having that would mean I could write fairly naive code without falling > into the trap of having something that fails when there are 2 > occurrences on the same page. I worked this out - the following code in my parser's __init__ does the job: self.count = getattr(request, 'Parser_counter_Count', 0) request.Parser_counter_Count = self.count + 1 What was going wrong in my earlier tests was that I was using a name starting with __ and Python mangles the name in that case (in the second line, but not in the first). Paul From steveo at syslang.net Wed Dec 7 23:37:32 2011 From: steveo at syslang.net (Steven W. Orr) Date: Wed, 07 Dec 2011 23:37:32 -0500 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? Message-ID: <4EE03F0C.4050409@syslang.net> Every day I get a a few people who create an account and create a spam page. It is getting boring. Only people who are logged in are allowed to create or modify a page. 1. Can I block people from creating an account if their address is from the .info TLD? 2. Can I send email to the person who tries to create an account that they have to respond to? Failure to respond would block final creation of the account. TIA -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net From ajhurst at me.com Thu Dec 8 00:31:53 2011 From: ajhurst at me.com (John Hurst) Date: Thu, 08 Dec 2011 16:31:53 +1100 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: <4EE03F0C.4050409@syslang.net> References: <4EE03F0C.4050409@syslang.net> Message-ID: <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> I had this problem. I explored the web page below, but couldn't get it to work. http://moinmo.in/FeatureRequests/DisableUserCreation Aftyer much trial and error, I eventually nurgled the _create_user routine in /MoinMoin/action/newaccount.py to add a couple of lines def _create_user(request): _ = request.getText form = request.form if not request.user.isSuperUser(): return _('You are not allowed to use this action.') ... which does the trick by allowing only superusers to create new accounts. However, it doesn't actually print the error message, but internal errors, for reasons I don't understand. Oh well, it was a simple fix. Perhaps someone else might explain what I'm doing wrong? cheers, --John Hurst --5 Fran Court, Glen Waverley, VIC 3150 ~ ~~~&#: -- ajhurst at mac.com +61 3 9803 9346 _..___ ---____ at ___H__ --(mob 0407 569 292) |_____[_|_________[__]_ -- http://homepage.mac.com/ajhurst/ oo oo oo O--O--O o=o -- -- If Christmas were all year round, what would you do? Live to Party, or be a Party to Life? On 20111208, at 15:37, Steven W. Orr wrote: > Every day I get a a few people who create an account and create a spam page. It > is getting boring. Only people who are logged in are allowed to create or modify > a page. > > 1. Can I block people from creating an account if their address is from the > .info TLD? > > 2. Can I send email to the person who tries to create an account that they have > to respond to? Failure to respond would block final creation of the account. > > TIA > > -- > Time flies like the wind. Fruit flies like a banana. Stranger things have .0. > happened but none stranger than this. Does your driver's license say Organ ..0 > Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 > individuals! What if this weren't a hypothetical question? > steveo at syslang.net > > ------------------------------------------------------------------------------ > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point of > discussion for anyone considering optimizing the pricing and packaging model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > _______________________________________________ > Moin-user mailing list > Moin-user at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/moin-user From steveo at syslang.net Thu Dec 8 10:05:31 2011 From: steveo at syslang.net (Steven W. Orr) Date: Thu, 08 Dec 2011 10:05:31 -0500 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> References: <4EE03F0C.4050409@syslang.net> <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> Message-ID: <4EE0D23B.9010600@syslang.net> On 12/8/2011 12:31 AM, John Hurst wrote: > I had this problem. I explored the web page below, but couldn't get it to work. > > http://moinmo.in/FeatureRequests/DisableUserCreation > > Aftyer much trial and error, I eventually nurgled the _create_user routine in/MoinMoin/action/newaccount.py to add a couple of lines > > def _create_user(request): > _ = request.getText > form = request.form > > if not request.user.isSuperUser(): > return _('You are not allowed to use this action.') > > ... > > which does the trick by allowing only superusers to create new accounts. However, it doesn't actually print the error message, but internal errors, for reasons I don't understand. Oh well, it was a simple fix. Perhaps someone else might explain what I'm doing wrong? This is not really what I want. I don't want other people to not be allowed to create accounts. What I want is to prevent people from creating accounts whose email address matches a pattern. In my case (today) the interlopers are all on the .info TLD Another thing that would be wonderful would be if the account creation could be completed only by responding to a confirmation email, the same as if you were signing up for a mailing list. But, I don't want to disallow everyone from signing up as a default. BTW, I should mention that all of the spam that I'm getting is not only coming from the .info TLD, it's also coming in despite TextCha being enabled. That never used to be the case. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net From rb.proj at gmail.com Thu Dec 8 11:05:04 2011 From: rb.proj at gmail.com (R.Bauer) Date: Thu, 08 Dec 2011 17:05:04 +0100 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: <4EE0D23B.9010600@syslang.net> References: <4EE03F0C.4050409@syslang.net> <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> <4EE0D23B.9010600@syslang.net> Message-ID: Hi read http://moinmo.in/HelpOnSpam and enable textchas cheers Reimar Am 08.12.2011 16:05, schrieb Steven W. Orr: > On 12/8/2011 12:31 AM, John Hurst wrote: >> I had this problem. I explored the web page below, but couldn't get it to work. >> >> http://moinmo.in/FeatureRequests/DisableUserCreation >> >> Aftyer much trial and error, I eventually nurgled the _create_user routine in/MoinMoin/action/newaccount.py to add a couple of lines >> >> def _create_user(request): >> _ = request.getText >> form = request.form >> >> if not request.user.isSuperUser(): >> return _('You are not allowed to use this action.') >> >> ... >> >> which does the trick by allowing only superusers to create new accounts. However, it doesn't actually print the error message, but internal errors, for reasons I don't understand. Oh well, it was a simple fix. Perhaps someone else might explain what I'm doing wrong? > > This is not really what I want. I don't want other people to not be allowed to > create accounts. What I want is to prevent people from creating accounts whose > email address matches a pattern. In my case (today) the interlopers are all on > the .info TLD > > Another thing that would be wonderful would be if the account creation could > be completed only by responding to a confirmation email, the same as if you > were signing up for a mailing list. > > But, I don't want to disallow everyone from signing up as a default. > > BTW, I should mention that all of the spam that I'm getting is not only coming > from the .info TLD, it's also coming in despite TextCha being enabled. That > never used to be the case. > From Nikolaus at rath.org Thu Dec 8 11:23:00 2011 From: Nikolaus at rath.org (Nikolaus Rath) Date: Thu, 08 Dec 2011 11:23:00 -0500 Subject: [Moin-user] Including page changes attachment path resolution In-Reply-To: <874nxt5hjt.fsf@vostro.rath.org> (Nikolaus Rath's message of "Thu, 24 Nov 2011 16:36:38 -0500") References: <874nxt5hjt.fsf@vostro.rath.org> Message-ID: <87iplrkp7f.fsf@inspiron.ap.columbia.edu> Hi, Really no one any idea? (Fullquote below in case the message got lost). Best, Nikolaus Nikolaus Rath writes: > Hello, > > I would like to include a static menu bar in every rendered page. The > menu bar itself should be editable as a page. > > I came up with the following code to include another page: > > def includepage(self, page_name): > request = self.request > inc_page = Page(request, page_name, formatter=request.formatter) > if not inc_page.exists(): > return '

Page %s does not exist

' % page_name > > strfile = StringIO.StringIO() > request.redirect(strfile) > try: > inc_page.send_page(content_only=True, > omit_footnotes=True, > count_hit=False) > return strfile.getvalue() > finally: > request.redirect() > > I then changed my theme's .py file to include the page "navibar": > > def navibarpanel(self, d): > html = [ > u'

Quick Links

', > self.navibar(d), > u'
', > > u'

Navigation

', > self.includepage('navibar'), > u'
', > ] > return u''.join(html) > > > This works nicely, but there is one problem: if, in any page, I refer to > an attachment as [[attachment:bla.zip]], then MoinMoin looks for bla.zip > in the "navibar" page rather than the page I'm actually viewing. > > > Is there a way to fix this problem? Or is my entire approach wrong? -Nikolaus -- ?Time flies like an arrow, fruit flies like a Banana.? PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C From steveo at syslang.net Thu Dec 8 12:53:06 2011 From: steveo at syslang.net (Steven W. Orr) Date: Thu, 08 Dec 2011 12:53:06 -0500 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: References: <4EE03F0C.4050409@syslang.net> <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> <4EE0D23B.9010600@syslang.net> Message-ID: <4EE0F982.7050200@syslang.net> On 12/8/2011 11:05 AM, R.Bauer wrote: > Hi > > read http://moinmo.in/HelpOnSpam and enable textchas > > > cheers > Reimar As I mentioned: ...it's also coming in despite TextCha being enabled. That never used to be the case. > > Am 08.12.2011 16:05, schrieb Steven W. Orr: >> On 12/8/2011 12:31 AM, John Hurst wrote: >>> I had this problem. I explored the web page below, but couldn't get it to work. >>> >>> http://moinmo.in/FeatureRequests/DisableUserCreation >>> >>> Aftyer much trial and error, I eventually nurgled the _create_user routine in/MoinMoin/action/newaccount.py to add a couple of lines >>> >>> def _create_user(request): >>> _ = request.getText >>> form = request.form >>> >>> if not request.user.isSuperUser(): >>> return _('You are not allowed to use this action.') >>> >>> ... >>> >>> which does the trick by allowing only superusers to create new accounts. However, it doesn't actually print the error message, but internal errors, for reasons I don't understand. Oh well, it was a simple fix. Perhaps someone else might explain what I'm doing wrong? >> >> This is not really what I want. I don't want other people to not be allowed to >> create accounts. What I want is to prevent people from creating accounts whose >> email address matches a pattern. In my case (today) the interlopers are all on >> the .info TLD >> >> Another thing that would be wonderful would be if the account creation could >> be completed only by responding to a confirmation email, the same as if you >> were signing up for a mailing list. >> >> But, I don't want to disallow everyone from signing up as a default. >> >> BTW, I should mention that all of the spam that I'm getting is not only coming >> from the .info TLD, it's also coming in despite TextCha being enabled. That >> never used to be the case. >> > > > > ------------------------------------------------------------------------------ > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point of > discussion for anyone considering optimizing the pricing and packaging model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > _______________________________________________ > Moin-user mailing list > Moin-user at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/moin-user -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net From paul at boddie.org.uk Thu Dec 8 17:00:24 2011 From: paul at boddie.org.uk (Paul Boddie) Date: Thu, 8 Dec 2011 23:00:24 +0100 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: <4EE0D23B.9010600@syslang.net> References: <4EE03F0C.4050409@syslang.net> <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> <4EE0D23B.9010600@syslang.net> Message-ID: <201112082300.25870.paul@boddie.org.uk> On Thursday 08 December 2011 16:05:31 Steven W. Orr wrote: > > This is not really what I want. I don't want other people to not be allowed > to create accounts. What I want is to prevent people from creating accounts > whose email address matches a pattern. In my case (today) the interlopers > are all on the .info TLD Are they all providing .info e-mail addresses or are their requests originating from addresses resolving to .info domains? It seems to me that spammers could easily work around restrictions on e-mail addresses. Nevertheless, you could just change the newaccount action to check the e-mail address. Something like this, after checking for the address's presence for an existing user and just before saving the new user... blocked_pattern = getattr(request.cfg, "blocked_email_addresses") if blocked_pattern: blocked_regexp = re.compile(blocked_pattern) if blocked_regexp.match(theuser.email): return _("Couldn't register you!") Feel free to use this, play around with it, use multiple patterns or whatever. I guess you'd set the pattern up like this: blocked_email_addresses = r".*?\.info$" You could use the | operator and brackets to add more possibilities. > Another thing that would be wonderful would be if the account creation > could be completed only by responding to a confirmation email, the same as > if you were signing up for a mailing list. I saw the following e-mail confirmation patch when searching the Moin site for "account creation": http://moinmo.in/RussellStuart/EmailActivation The discussion is a bit weird because a lot of the timestamps give the current time instead of the time of each message, but it seems that people have been looking at this code and the problem in general fairly recently. > But, I don't want to disallow everyone from signing up as a default. > > BTW, I should mention that all of the spam that I'm getting is not only > coming from the .info TLD, it's also coming in despite TextCha being > enabled. That never used to be the case. It's possible that determined people could target a site using TextCha and defeat it, but that goes somewhat beyond what TextCha is designed to handle. With regard to general frameworks around the mechanisms discussed here, the new account action doesn't seem to utilise any event mechanisms that you find elsewhere in Moin, so you can't write a plug-in that performs a post-registration check. I experimented with an event handler that performs authorisation checks on edits: http://moinmo.in/ActionMarket/ApproveChanges This is a potentially large sledgehammer to crack the nut of spam, however, but it effectively queues all edits from anyone you haven't explicitly nominated as being trustworthy. Spammers shouldn't see any of their edits published unless you approve them. Paul From rb.proj at gmail.com Fri Dec 9 03:50:10 2011 From: rb.proj at gmail.com (R.Bauer) Date: Fri, 09 Dec 2011 09:50:10 +0100 Subject: [Moin-user] Including page changes attachment path resolution In-Reply-To: <87iplrkp7f.fsf@inspiron.ap.columbia.edu> References: <874nxt5hjt.fsf@vostro.rath.org> <87iplrkp7f.fsf@inspiron.ap.columbia.edu> Message-ID: Am 08.12.2011 17:23, schrieb Nikolaus Rath: > Hi, > > Really no one any idea? (Fullquote below in case the message got lost). > Hi some ideas: * you may be want to use formatter.page.page_name * there are themes on the ThemeMarket with an editable Sidebar based on a wiki page, see http://moinmo.in/ThemeMarket/Mandarin * wikiutil.renderText is also your friend. Reimar > Best, > Nikolaus > > > Nikolaus Rath writes: >> Hello, >> >> I would like to include a static menu bar in every rendered page. The >> menu bar itself should be editable as a page. >> >> I came up with the following code to include another page: >> >> def includepage(self, page_name): >> request = self.request >> inc_page = Page(request, page_name, formatter=request.formatter) >> if not inc_page.exists(): >> return '

Page %s does not exist

' % page_name >> >> strfile = StringIO.StringIO() >> request.redirect(strfile) >> try: >> inc_page.send_page(content_only=True, >> omit_footnotes=True, >> count_hit=False) >> return strfile.getvalue() >> finally: >> request.redirect() >> >> I then changed my theme's .py file to include the page "navibar": >> >> def navibarpanel(self, d): >> html = [ >> u'

Quick Links

', >> self.navibar(d), >> u'
', >> >> u'

Navigation

', >> self.includepage('navibar'), >> u'
', >> ] >> return u''.join(html) >> >> >> This works nicely, but there is one problem: if, in any page, I refer to >> an attachment as [[attachment:bla.zip]], then MoinMoin looks for bla.zip >> in the "navibar" page rather than the page I'm actually viewing. >> >> >> Is there a way to fix this problem? Or is my entire approach wrong? > > > -Nikolaus > From rb.proj at gmail.com Fri Dec 9 03:53:54 2011 From: rb.proj at gmail.com (R.Bauer) Date: Fri, 09 Dec 2011 09:53:54 +0100 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: <4EE0F982.7050200@syslang.net> References: <4EE03F0C.4050409@syslang.net> <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> <4EE0D23B.9010600@syslang.net> <4EE0F982.7050200@syslang.net> Message-ID: Am 08.12.2011 18:53, schrieb Steven W. Orr: > On 12/8/2011 11:05 AM, R.Bauer wrote: >> Hi >> >> read http://moinmo.in/HelpOnSpam and enable textchas >> >> >> cheers >> Reimar > > As I mentioned: > > ...it's also coming in despite TextCha being enabled. That never used to be > the case. > You can use a textcha only you can answer. Then only people in your group which don't be annoyed by textchas can create accounts by the newaccount action for others. Reimar >> >> Am 08.12.2011 16:05, schrieb Steven W. Orr: >>> On 12/8/2011 12:31 AM, John Hurst wrote: >>>> I had this problem. I explored the web page below, but couldn't get it to work. >>>> >>>> http://moinmo.in/FeatureRequests/DisableUserCreation >>>> >>>> Aftyer much trial and error, I eventually nurgled the _create_user routine in/MoinMoin/action/newaccount.py to add a couple of lines >>>> >>>> def _create_user(request): >>>> _ = request.getText >>>> form = request.form >>>> >>>> if not request.user.isSuperUser(): >>>> return _('You are not allowed to use this action.') >>>> >>>> ... >>>> >>>> which does the trick by allowing only superusers to create new accounts. However, it doesn't actually print the error message, but internal errors, for reasons I don't understand. Oh well, it was a simple fix. Perhaps someone else might explain what I'm doing wrong? >>> >>> This is not really what I want. I don't want other people to not be allowed to >>> create accounts. What I want is to prevent people from creating accounts whose >>> email address matches a pattern. In my case (today) the interlopers are all on >>> the .info TLD >>> >>> Another thing that would be wonderful would be if the account creation could >>> be completed only by responding to a confirmation email, the same as if you >>> were signing up for a mailing list. >>> >>> But, I don't want to disallow everyone from signing up as a default. >>> >>> BTW, I should mention that all of the spam that I'm getting is not only coming >>> from the .info TLD, it's also coming in despite TextCha being enabled. That >>> never used to be the case. >>> >> >> >> >> ------------------------------------------------------------------------------ >> Cloud Services Checklist: Pricing and Packaging Optimization >> This white paper is intended to serve as a reference, checklist and point of >> discussion for anyone considering optimizing the pricing and packaging model >> of a cloud services business. Read Now! >> http://www.accelacomm.com/jaw/sfnl/114/51491232/ >> _______________________________________________ >> Moin-user mailing list >> Moin-user at lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/moin-user > > From rb.proj at gmail.com Fri Dec 9 03:55:56 2011 From: rb.proj at gmail.com (R.Bauer) Date: Fri, 09 Dec 2011 09:55:56 +0100 Subject: [Moin-user] Can I block people from creating accounts if they don't verify their address? In-Reply-To: <201112082300.25870.paul@boddie.org.uk> References: <4EE03F0C.4050409@syslang.net> <7AFAF904-4244-4792-BE8B-810534E3EC2D@me.com> <4EE0D23B.9010600@syslang.net> <201112082300.25870.paul@boddie.org.uk> Message-ID: Hi just a note, moin2 approves accounts by email. Reimar Am 08.12.2011 23:00, schrieb Paul Boddie: > On Thursday 08 December 2011 16:05:31 Steven W. Orr wrote: >> >> This is not really what I want. I don't want other people to not be allowed >> to create accounts. What I want is to prevent people from creating accounts >> whose email address matches a pattern. In my case (today) the interlopers >> are all on the .info TLD > > Are they all providing .info e-mail addresses or are their requests > originating from addresses resolving to .info domains? It seems to me that > spammers could easily work around restrictions on e-mail addresses. > Nevertheless, you could just change the newaccount action to check the e-mail > address. Something like this, after checking for the address's presence for > an existing user and just before saving the new user... > > blocked_pattern = getattr(request.cfg, "blocked_email_addresses") > if blocked_pattern: > blocked_regexp = re.compile(blocked_pattern) > if blocked_regexp.match(theuser.email): > return _("Couldn't register you!") > > Feel free to use this, play around with it, use multiple patterns or whatever. > I guess you'd set the pattern up like this: > > blocked_email_addresses = r".*?\.info$" > > You could use the | operator and brackets to add more possibilities. > >> Another thing that would be wonderful would be if the account creation >> could be completed only by responding to a confirmation email, the same as >> if you were signing up for a mailing list. > > I saw the following e-mail confirmation patch when searching the Moin site > for "account creation": > > http://moinmo.in/RussellStuart/EmailActivation > > The discussion is a bit weird because a lot of the timestamps give the current > time instead of the time of each message, but it seems that people have been > looking at this code and the problem in general fairly recently. > >> But, I don't want to disallow everyone from signing up as a default. >> >> BTW, I should mention that all of the spam that I'm getting is not only >> coming from the .info TLD, it's also coming in despite TextCha being >> enabled. That never used to be the case. > > It's possible that determined people could target a site using TextCha and > defeat it, but that goes somewhat beyond what TextCha is designed to handle. > > With regard to general frameworks around the mechanisms discussed here, the > new account action doesn't seem to utilise any event mechanisms that you find > elsewhere in Moin, so you can't write a plug-in that performs a > post-registration check. I experimented with an event handler that performs > authorisation checks on edits: > > http://moinmo.in/ActionMarket/ApproveChanges > > This is a potentially large sledgehammer to crack the nut of spam, however, > but it effectively queues all edits from anyone you haven't explicitly > nominated as being trustworthy. Spammers shouldn't see any of their edits > published unless you approve them. > > Paul > > ------------------------------------------------------------------------------ > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point of > discussion for anyone considering optimizing the pricing and packaging model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ From Nikolaus at rath.org Fri Dec 9 09:33:36 2011 From: Nikolaus at rath.org (Nikolaus Rath) Date: Fri, 09 Dec 2011 09:33:36 -0500 Subject: [Moin-user] Including page changes attachment path resolution In-Reply-To: (R. Bauer's message of "Fri, 09 Dec 2011 09:50:10 +0100") References: <874nxt5hjt.fsf@vostro.rath.org> <87iplrkp7f.fsf@inspiron.ap.columbia.edu> Message-ID: <87ehwdn7b3.fsf@inspiron.ap.columbia.edu> "R.Bauer" writes: > Am 08.12.2011 17:23, schrieb Nikolaus Rath: >>> I would like to include a static menu bar in every rendered page. The >>> menu bar itself should be editable as a page. >>> >>> I came up with the following code to include another page: >>> >>> def includepage(self, page_name): >>> request = self.request >>> inc_page = Page(request, page_name, formatter=request.formatter) >>> if not inc_page.exists(): >>> return '

Page %s does not exist

' % page_name >>> >>> strfile = StringIO.StringIO() >>> request.redirect(strfile) >>> try: >>> inc_page.send_page(content_only=True, >>> omit_footnotes=True, >>> count_hit=False) >>> return strfile.getvalue() >>> finally: >>> request.redirect() >>> >>> This works nicely, but there is one problem: if, in any page, I refer to >>> an attachment as [[attachment:bla.zip]], then MoinMoin looks for bla.zip >>> in the "navibar" page rather than the page I'm actually viewing. > > some ideas: > * you may be want to use formatter.page.page_name > > * there are themes on the ThemeMarket with an editable Sidebar based > on a wiki page, see http://moinmo.in/ThemeMarket/Mandarin > > * wikiutil.renderText is also your friend. Thanks! I worked backwards from the Mandarin theme and found that the following works: inc_page = Page(request, page_name) while this messes up the references: inc_page = Page(request, page_name, formatter=request.formatter Can anyone explain to me why the second form is wrong? Best, -Nikolaus -- ?Time flies like an arrow, fruit flies like a Banana.? PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C From Nikolaus at rath.org Fri Dec 9 09:42:41 2011 From: Nikolaus at rath.org (Nikolaus Rath) Date: Fri, 09 Dec 2011 09:42:41 -0500 Subject: [Moin-user] Deleting Page doesn't delete attachments Message-ID: <87borhn6vy.fsf@inspiron.ap.columbia.edu> Hello, I noticed that when I delete a page, the page attachments are not deleted. Is that a bug or a feature? Is there a way to automatically delete attachments with the page? Is there a way to list all "orphaned" attachments whose page has been deleted, so that I can clean them up? Thanks! -Nikolaus -- ?Time flies like an arrow, fruit flies like a Banana.? PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C From tw-public at gmx.de Mon Dec 12 13:01:32 2011 From: tw-public at gmx.de (Thomas Waldmann) Date: Mon, 12 Dec 2011 19:01:32 +0100 Subject: [Moin-user] new moin2 theme In-Reply-To: <201111240045.00733.paul@boddie.org.uk> References: <201111212339.22422.paul@boddie.org.uk> <1322065664.16823.8.camel@server.firma.waldmann-edv.de> <201111240045.00733.paul@boddie.org.uk> Message-ID: <1323712892.17912.15.camel@server.firma.waldmann-edv.de> the good news: I am currently working on a new moin2 theme. I did a clean start from zero, NOT copying complete old css. Currently, the "show" view already looks quite nice (lots of other stuff is still very broken): wide screen: http://img1.uploadscreenshot.com/images/orig/12/34421575874-orig.png narrow screen: http://img1.uploadscreenshot.com/images/orig/12/34422093566-orig.png as you see there, there is still quite some css missing (e.g. those paragraph symbols in the headlines should be hidden usually). I will try to get that stuff to a "not totally broken" state ASAP (before pushing it to main repo), so we maybe can even have some Google Code-In theme tasks. btw, I need a name for that theme, currently it is named "foobar". the bad news: * it might be that while cleaning up the whole html/css/layout mess, I have to break compatibility to the moin2 modernized theme as it is now. * flask-themes extension is broken for loading templates from the theme for flask >= 0.8 (which we use), I did a quick fix, but have no idea whether it is complete, see the flask-themes issue tracker. as long as we can't easily get a fixed version/release for that, this is a blocker (or at least a major annoyance). From rb.proj at gmail.com Mon Dec 12 13:53:03 2011 From: rb.proj at gmail.com (R.Bauer) Date: Mon, 12 Dec 2011 19:53:03 +0100 Subject: [Moin-user] Deleting Page doesn't delete attachments In-Reply-To: <87borhn6vy.fsf@inspiron.ap.columbia.edu> References: <87borhn6vy.fsf@inspiron.ap.columbia.edu> Message-ID: Am 09.12.2011 15:42, schrieb Nikolaus Rath: > Hello, Moin > > I noticed that when I delete a page, the page attachments are not > deleted. Is that a bug or a feature? feature > > Is there a way to automatically delete attachments with the page? I ususally rename pages tp Delete_ prefix and clean it them up regulary on the server. e.g. moin ... maint cleanpage ... If xmlrpc is enabled you can delete by that too. > > Is there a way to list all "orphaned" attachments whose page has been > deleted, so that I can clean them up? That is implemented in moin2. We don't have that in moin1 Reimar > > > Thanks! > > -Nikolaus > From creasyimm at gmail.com Tue Dec 13 08:38:19 2011 From: creasyimm at gmail.com (=?GB2312?B?y8671A==?=) Date: Tue, 13 Dec 2011 21:38:19 +0800 Subject: [Moin-user] About moinmoin cas authentication Message-ID: Hi?all Recently, I want to make moinmoin?1.9.3?single wiki?installed ok? work wiht a cas server(rubycas server). Here is my problem?I modified related file?cas.py at right path?and wikiconfig.py is modified correctly?. When I try to login form cas server, I found out the redirect url is somehow not in the right fomat? 192.168.27.4 is wiki server 192.168.25.11 is cas server Here is information from cas server ----------------------------------------------------------------------------------------------------------- *bogon - - [13/Dec/2011:19:29:23 CST] "GET /cas/login?service=http%3A%2F%2F192.168.27.4%2F%252FLanguageSetup HTTP/1.1" 200 2473 **http://192.168.27.4/* * -> /cas/login?service=http%3A%2F%2F192.168.27.4%2F%252FLanguageSetup bogon - - [13/Dec/2011:19:29:29 CST] "POST /cas/login HTTP/1.1" 303 0 **http://192.168.25.11/cas/login?service=http%3A%2F%2F192.168.27.4%2F%252F LanguageSetup* * -> /cas/login* ----------------------------------------------------------------------------------------------------------- After the cas server redirect back to wiki page?instead of showing the page before login?some thing like this ----------------------------------------------------------------------------------------------------------- *Not Found* *The requested URL //LanguageSetup was not found on this server.* ----------------------------------------------------------------------------------------------------------- I think the service string was wrong?one more ?/?comes out? I am not familiar with python language, Please help me~? Thanks a lot~? Best Regards??? 2011-12-13 ------------------------------ creasy -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.scheufele at diasemi.com Wed Dec 14 10:14:22 2011 From: mark.scheufele at diasemi.com (Mark Scheufele) Date: Wed, 14 Dec 2011 15:14:22 +0000 Subject: [Moin-user] wiki does not display the latest revision of a page Message-ID: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> Hi Moin users, I am currently experiencing a strange problem with a page within our wiki installation (we are running revision 1.9.3). The problem is that NOT the latest revision of the page is being displayed. When I open the page in question it shows at the bottom the time and the user who did apply the latest changes. This info shows IT/SA/Sites/Tokyo/UNIX (last edited 2011-11-22 11:56:45 by uabdulla) When I open the page history I can see that several changes have been applied after that particular revision: 36 2011-12-14 15:38:04 3069 to previous mscheufe now everything should be back to normal (ms) view 35 2011-12-14 15:37:13 2901 to previous mscheufe there are edits missing in the current revision 34 view 34 2011-12-14 12:14:37 3069 to previous chlewis view 33 2011-12-14 12:10:52 2901 to previous chlewis view 32 2011-11-22 11:56:45 2492 to previous uabdulha + synchronicity server alias name (mas-tokyo) <- THIS IS THE REVISION THAT IS BEING DISPLAYED When I look into the page directory of the page I can see that the current file holds the revision 00000036 which is correct. When I look into the revisions directory all the revisions are there and the revision 00000036 has all latest changes. Also when I click on the view button for revision 00000036 the correct version of the page is displayed. So I am having the following questions: - why does the software display revision 00000032 and not the latest revision 00000036? - does anybody know how to resolve the problem? This is the first time that we are running in such an issue. Until today the software was running fine for more than a year. Many Thanks for your help. mark _______________________________________________________________________________________ Dialog Semiconductor GmbH Neue Str. 95 D-73230 Kirchheim Managing Directors: Dr. Jalal Bagherli, Jean-Michel Richard Chairman of the Supervisory Board: Gregorio Reyes Commercial register: Amtsgericht Stuttgart: HRB 231181 UST-ID-Nr. DE 811121668 Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and contains proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please consider the environment before printing this e-mail From tw-public at gmx.de Wed Dec 14 12:01:10 2011 From: tw-public at gmx.de (Thomas Waldmann) Date: Wed, 14 Dec 2011 18:01:10 +0100 Subject: [Moin-user] wiki does not display the latest revision of a page In-Reply-To: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> References: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> Message-ID: <1323882070.28797.4.camel@server.firma.waldmann-edv.de> Hi Mark, > I am currently experiencing a strange problem with a page within our wiki installation (we are running revision 1.9.3). > The problem is that NOT the latest revision of the page is being displayed. > ... > When I look into the page directory of the page I can see that the current file holds the revision 00000036 which is correct. If the "current" file is correct, then I suspect that there might be some cache issue. Can you try "clear cache" from "more actions" menu? > - why does the software display revision 00000032 and not the latest revision 00000036? That's a good question. Usually the cache for the "precompiled" wiki page only gets updated from the current revision, it doesn't cache non-current revisions. Cheers, Thomas From mark.scheufele at diasemi.com Wed Dec 14 12:24:18 2011 From: mark.scheufele at diasemi.com (Mark Scheufele) Date: Wed, 14 Dec 2011 17:24:18 +0000 Subject: [Moin-user] wiki does not display the latest revision of a page In-Reply-To: <1323882070.28797.4.camel@server.firma.waldmann-edv.de> References: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> <1323882070.28797.4.camel@server.firma.waldmann-edv.de> Message-ID: <39080CC9D403A94F992B5A8183FE77BC3FE75D9A@NB-EX-MBX01.diasemi.com> Hallo Thomas, thanks for the tip I did carry out the "Delete Cache" command from the "more options" menu and it apparently solved the problem. Is every user who has read,write,delete,revert,admin rights for the page able to carry out the "Delete Cache" command? Thanks for your help, mark -----Original Message----- From: Thomas Waldmann [mailto:tw-public at gmx.de] Sent: Mittwoch, 14. Dezember 2011 18:01 To: Mark Scheufele Cc: moin-user at lists.sourceforge.net Subject: Re: [Moin-user] wiki does not display the latest revision of a page Hi Mark, > I am currently experiencing a strange problem with a page within our wiki installation (we are running revision 1.9.3). > The problem is that NOT the latest revision of the page is being displayed. > ... > When I look into the page directory of the page I can see that the current file holds the revision 00000036 which is correct. If the "current" file is correct, then I suspect that there might be some cache issue. Can you try "clear cache" from "more actions" menu? > - why does the software display revision 00000032 and not the latest revision 00000036? That's a good question. Usually the cache for the "precompiled" wiki page only gets updated from the current revision, it doesn't cache non-current revisions. Cheers, Thomas _______________________________________________________________________________________ Dialog Semiconductor GmbH Neue Str. 95 D-73230 Kirchheim Managing Directors: Dr. Jalal Bagherli, Jean-Michel Richard Chairman of the Supervisory Board: Gregorio Reyes Commercial register: Amtsgericht Stuttgart: HRB 231181 UST-ID-Nr. DE 811121668 Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and contains proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please consider the environment before printing this e-mail From hugo at lip.pt Thu Dec 15 06:44:51 2011 From: hugo at lip.pt (Hugo Gomes) Date: Thu, 15 Dec 2011 11:44:51 +0000 Subject: [Moin-user] New Accounts Message-ID: <1323949491.2056.5.camel@lnsys16.lip.pt> Hi all, How can i configure my moinmoin to send email to superuser or a predefined email, each time a new account is created? Best Regards, -- ************************************************* Hugo Gomes LIP Av. Elias Garcia 14, 1? 1000-149 Lisboa, Portugal Telef.: +351- 217 998 587 URL: http://www.lip.pt E-mail: hugo at lip.pt ************************************************* From hugo at lip.pt Thu Dec 15 07:06:18 2011 From: hugo at lip.pt (Hugo Gomes) Date: Thu, 15 Dec 2011 12:06:18 +0000 Subject: [Moin-user] New Accounts In-Reply-To: <1323949491.2056.5.camel@lnsys16.lip.pt> References: <1323949491.2056.5.camel@lnsys16.lip.pt> Message-ID: <1323950778.2056.7.camel@lnsys16.lip.pt> I've found out to do it. I was looking in the hard way, somewhere in the configuration files, but now i've found it in the web interface in my settings->notification area. Regards, Hugo Gomes On Thu, 2011-12-15 at 11:44 +0000, Hugo Gomes wrote: > Hi all, > > How can i configure my moinmoin to send email to superuser or a > predefined email, each time a new account is created? > > Best Regards, > -- ************************************************* Hugo Gomes LIP Av. Elias Garcia 14, 1? 1000-149 Lisboa, Portugal Telef.: +351- 217 998 587 URL: http://www.lip.pt E-mail: hugo at lip.pt ************************************************* From tw-public at gmx.de Thu Dec 15 07:52:09 2011 From: tw-public at gmx.de (Thomas Waldmann) Date: Thu, 15 Dec 2011 13:52:09 +0100 Subject: [Moin-user] wiki does not display the latest revision of a page In-Reply-To: <39080CC9D403A94F992B5A8183FE77BC3FE75D9A@NB-EX-MBX01.diasemi.com> References: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> <1323882070.28797.4.camel@server.firma.waldmann-edv.de> <39080CC9D403A94F992B5A8183FE77BC3FE75D9A@NB-EX-MBX01.diasemi.com> Message-ID: <1323953529.3189.1.camel@server.firma.waldmann-edv.de> > thanks for the tip I did carry out the "Delete Cache" command from the "more options" menu and it apparently solved the problem. > Is every user who has read,write,delete,revert,admin rights for the page able to carry out the "Delete Cache" command? Yes, you do not even need admin for that. If you have more pages with that issue, you could also do a "moin ... maint cleancache" on the shell. From mark.scheufele at diasemi.com Fri Dec 16 05:04:42 2011 From: mark.scheufele at diasemi.com (Mark Scheufele) Date: Fri, 16 Dec 2011 10:04:42 +0000 Subject: [Moin-user] wiki does not display the latest revision of a page In-Reply-To: <1323953529.3189.1.camel@server.firma.waldmann-edv.de> References: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> <1323882070.28797.4.camel@server.firma.waldmann-edv.de> <39080CC9D403A94F992B5A8183FE77BC3FE75D9A@NB-EX-MBX01.diasemi.com> <1323953529.3189.1.camel@server.firma.waldmann-edv.de> Message-ID: <39080CC9D403A94F992B5A8183FE77BC3FE773D1@NB-EX-MBX01.diasemi.com> Hi Thomas, once again thanks for your help and one last question on that topic. Would I have to stop the wiki software to run the "maint cleancache" command or can I run it while the wiki is running? mark -----Original Message----- From: Thomas Waldmann [mailto:tw-public at gmx.de] Sent: Donnerstag, 15. Dezember 2011 13:52 To: moin-user at lists.sourceforge.net Subject: Re: [Moin-user] wiki does not display the latest revision of a page > thanks for the tip I did carry out the "Delete Cache" command from the "more options" menu and it apparently solved the problem. > Is every user who has read,write,delete,revert,admin rights for the page able to carry out the "Delete Cache" command? Yes, you do not even need admin for that. If you have more pages with that issue, you could also do a "moin ... maint cleancache" on the shell. ------------------------------------------------------------------------------ 10 Tips for Better Server Consolidation Server virtualization is being driven by many needs. But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! http://www.accelacomm.com/jaw/sdnl/114/51507609/ _______________________________________________ Moin-user mailing list Moin-user at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user _______________________________________________________________________________________ Dialog Semiconductor GmbH Neue Str. 95 D-73230 Kirchheim Managing Directors: Dr. Jalal Bagherli, Jean-Michel Richard Chairman of the Supervisory Board: Gregorio Reyes Commercial register: Amtsgericht Stuttgart: HRB 231181 UST-ID-Nr. DE 811121668 Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and contains proprietary information, some or all of which may be legally privileged. It is intended solely for the use of the individual or entity to which it is addressed. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please consider the environment before printing this e-mail From tw-public at gmx.de Fri Dec 16 09:45:25 2011 From: tw-public at gmx.de (Thomas Waldmann) Date: Fri, 16 Dec 2011 15:45:25 +0100 Subject: [Moin-user] wiki does not display the latest revision of a page In-Reply-To: <39080CC9D403A94F992B5A8183FE77BC3FE773D1@NB-EX-MBX01.diasemi.com> References: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> <1323882070.28797.4.camel@server.firma.waldmann-edv.de> <39080CC9D403A94F992B5A8183FE77BC3FE75D9A@NB-EX-MBX01.diasemi.com> <1323953529.3189.1.camel@server.firma.waldmann-edv.de> <39080CC9D403A94F992B5A8183FE77BC3FE773D1@NB-EX-MBX01.diasemi.com> Message-ID: <1324046725.10591.1.camel@server.firma.waldmann-edv.de> > Would I have to stop the wiki software to run the "maint cleancache" command or can I run it > while the wiki is running? While it might work while running the wiki engine, you better stop it to make sure there is no interference and really all gets cleaned up. It's usually just a matter of seconds. From jilingshu at gmail.com Tue Dec 20 01:27:08 2011 From: jilingshu at gmail.com (Bear) Date: Tue, 20 Dec 2011 14:27:08 +0800 Subject: [Moin-user] How to install a wikifarm based on path instead of sub-domain? Message-ID: <4EF02ABC.20303@Gmail.com> hi there, I am trying to install a MoinMoin wiki with wikifarm which may host many wikis on a single MoinMoin instance. However, I have only one domain available: http://wiki.example.org/, and I wanna host different wikis in sub-directory such as http://wiki.example.org/alpha http://wiki.example.org/beta I configured my farmconfig.py like this: [code] wikis = [ ("alpha", r"^http://wiki.example.org/alpha/.*$") ] [/code] and I an able to access "http://wiki.example.org/alpha/". However, all spacial pages are nonfunctional, they all point to, such as "http://wiki.example.org/HelpContents" instead of "http://wiki.example.org/alpha/HelpContents". How can I fix this? Thanks in advanced. From nicozanf at gmail.com Tue Dec 20 09:00:52 2011 From: nicozanf at gmail.com (Nico Zanferrari) Date: Tue, 20 Dec 2011 15:00:52 +0100 Subject: [Moin-user] How to install a wikifarm based on path instead of sub-domain? In-Reply-To: <4EF02ABC.20303@Gmail.com> References: <4EF02ABC.20303@Gmail.com> Message-ID: 2011/12/20 Bear : > > I configured my farmconfig.py like this: > [code] Moin Bear! Briefly, this is not enough ... Follow my HowTo on http://moinmo.in/HowTo/UbuntuFarm for detailed instructions! Cheers, Nico From rb.proj at gmail.com Wed Dec 21 02:36:03 2011 From: rb.proj at gmail.com (R.Bauer) Date: Wed, 21 Dec 2011 08:36:03 +0100 Subject: [Moin-user] wiki does not display the latest revision of a page In-Reply-To: <39080CC9D403A94F992B5A8183FE77BC3FE773D1@NB-EX-MBX01.diasemi.com> References: <39080CC9D403A94F992B5A8183FE77BC3FE74CC6@NB-EX-MBX01.diasemi.com> <1323882070.28797.4.camel@server.firma.waldmann-edv.de> <39080CC9D403A94F992B5A8183FE77BC3FE75D9A@NB-EX-MBX01.diasemi.com> <1323953529.3189.1.camel@server.firma.waldmann-edv.de> <39080CC9D403A94F992B5A8183FE77BC3FE773D1@NB-EX-MBX01.diasemi.com> Message-ID: Am 16.12.2011 11:04, schrieb Mark Scheufele: > Hi Thomas, > > once again thanks for your help and one last question on that topic. Would I have to stop the wiki software to run the "maint cleancache" command or can I run it > while the wiki is running? > > mark Just a question Can it be that you have altered those pages directly on the filesystem level without using the cli interface? Or Have you done a mighration beforhand to an other python or moin version and haven't called the cli command to clear the cache? Reimar > > -----Original Message----- > From: Thomas Waldmann [mailto:tw-public at gmx.de] > Sent: Donnerstag, 15. Dezember 2011 13:52 > To: moin-user at lists.sourceforge.net > Subject: Re: [Moin-user] wiki does not display the latest revision of a page > > >> thanks for the tip I did carry out the "Delete Cache" command from the "more options" menu and it apparently solved the problem. >> Is every user who has read,write,delete,revert,admin rights for the page able to carry out the "Delete Cache" command? > > Yes, you do not even need admin for that. > > If you have more pages with that issue, you could also do a "moin ... > maint cleancache" on the shell. > > > > ------------------------------------------------------------------------------ > 10 Tips for Better Server Consolidation > Server virtualization is being driven by many needs. > But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! > http://www.accelacomm.com/jaw/sdnl/114/51507609/ > _______________________________________________ > Moin-user mailing list > Moin-user at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/moin-user > _______________________________________________________________________________________ > > Dialog Semiconductor GmbH > Neue Str. 95 > D-73230 Kirchheim > Managing Directors: Dr. Jalal Bagherli, Jean-Michel Richard > Chairman of the Supervisory Board: Gregorio Reyes > Commercial register: Amtsgericht Stuttgart: HRB 231181 > UST-ID-Nr. DE 811121668 > > > Legal Disclaimer: This e-mail communication (and any attachment/s) is confidential and > contains proprietary information, some or all of which may be legally privileged. It is > intended solely for the use of the individual or entity to which it is addressed. Access > to this email by anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be taken in reliance > on it, is prohibited and may be unlawful. > > Please consider the environment before printing this e-mail > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure From jilingshu at gmail.com Wed Dec 21 06:47:26 2011 From: jilingshu at gmail.com (Bear) Date: Wed, 21 Dec 2011 19:47:26 +0800 Subject: [Moin-user] How to install a wikifarm based on path instead of sub-domain? In-Reply-To: References: <4EF02ABC.20303@Gmail.com> Message-ID: <4EF1C74E.8060409@Gmail.com> hi there, After read your instruction, I am still confused... :-( I have already copied "config/wikifarm/mywiki.py" as "fws.py" file and configured the "data" path, I don't know anything else I should do. Thanks. On 100/12/20 ?? 10:00, Nico Zanferrari wrote: > 2011/12/20 Bear: >> >> I configured my farmconfig.py like this: >> [code] > > > Moin Bear! > > Briefly, this is not enough ... Follow my HowTo on > http://moinmo.in/HowTo/UbuntuFarm for detailed instructions! > > > Cheers, > Nico > From jilingshu at gmail.com Wed Dec 21 07:34:45 2011 From: jilingshu at gmail.com (Bear) Date: Wed, 21 Dec 2011 20:34:45 +0800 Subject: [Moin-user] How to install a wikifarm based on path instead of sub-domain? In-Reply-To: <20111221122324.GI74323@cmd.bsdserwis.com> References: <4EF02ABC.20303@Gmail.com> <20111221122324.GI74323@cmd.bsdserwis.com> Message-ID: <4EF1D265.30609@Gmail.com> hi, Ahh, I am running my Moin wiki on Passenger instead of mod_wsgi for my hosting provider Dreamhost only support Passenger. :-( http://wiki.dreamhost.com/Passenger_WSGI On 100/12/21 ?? 08:23, Krzysztof Stryjek wrote: > Hello, > > On Tue, Dec 20, 2011 at 02:27:08PM +0800, Bear wrote: >> hi there, >> I am trying to install a MoinMoin wiki with wikifarm which may host many >> wikis on a single MoinMoin instance. However, I have only one domain >> available: http://wiki.example.org/, and I wanna host different wikis in >> sub-directory such as >> http://wiki.example.org/alpha >> http://wiki.example.org/beta >> >> I configured my farmconfig.py like this: >> [code] >> wikis = [ >> ("alpha", r"^http://wiki.example.org/alpha/.*$") >> ] >> [/code] >> and I an able to access "http://wiki.example.org/alpha/". However, all >> spacial pages are nonfunctional, they all point to, such as >> "http://wiki.example.org/HelpContents" instead of >> "http://wiki.example.org/alpha/HelpContents". How can I fix this? >> Thanks in advanced. >> > And did you modified http server (apache) configuration? > > ServerName wiki.example.org > RewriteEngine On > RewriteRule ^/alpha(.*)$ /path/to/moin/farmwiki/moin.cgi$1 [type=application/x-httpd-cgi,L] > RewriteRule ^/beta(.*)$ /path/to/moin/farmwiki/moin.cgi$1 [type=application/x-httpd-cgi,L] > > Greetings, From tw-public at gmx.de Sat Dec 24 21:25:17 2011 From: tw-public at gmx.de (Thomas Waldmann) Date: Sun, 25 Dec 2011 03:25:17 +0100 Subject: [Moin-user] MoinMoin at 28c3, Berlin Message-ID: <1324779917.5457.7.camel@x300.localdomain> In case you are at the 28c3 or at least near Berlin at end of december, you might be interested in the workshop or just to meet some of us there: http://moinmo.in/28c3 Caution: If you do not have one already, you'ld need a day ticket for the congress - these are maybe hard to get. If you don't attend the congress, but want to meet some of us nevertheless, please contact me by e-mail, maybe we can arrange something at dinner time (2011-12-27 .. 2011-12-30).