- Zope-Dev - Zope lists

NotMail
by Brian Takashi Hooper 13 Jan '00

13 Jan '00

Hi there - Does anyone have a copy of NotMail lying around anywhere that they could send me? I couldn't find it anymore on the Zope site... --Brian Hooper

1 0

Re: [Zope-dev] Authentication Patch
by Esben Haabendal Soerensen 13 Jan '00

13 Jan '00

>>>>> "Evan" == Evan Simpson <evan(a)4-am.com> writes: Evan> I got tired of dealing with the weird mechanics cookie-based Evan> logins have to deal with, where standard_html_error and Evan> tracebacks intrude on login intercepts. I came up with the Evan> following minor change, which works great for me, and might make Evan> GenericUserFolder's job easier, too. Evan> In ZPublisher/HTTPRequest.py (or SiteAccess/ChangeBehaviors.py, Evan> if you use SiteAccess), change the lines: Evan> if user is None and roles != UNSPECIFIED_ROLES: Evan> response.unauthorized() to: if user is None and roles != Evan> UNSPECIFIED_ROLES: object = response.unauthorized Evan> Under normal circumstances, this has no effect, since Evan> 'response.unauthorized' will be called as soon as it is returned Evan> and will raise its exception as usual. Now however, we add a Evan> twist; When the cookie-based authenticator fails, it replaces Evan> 'response.unauthorized' with its 'login' document. If no Evan> higher-level authentication succeeds, the 'login' document is Evan> rendered normally. Since 'response' is re-created with each Evan> request, this modification has no effect beyond the current Evan> request. Evan> What do you folks think? Nice. I wouldn't mind seeing this go into next release of GUF. /bart -- caffeine low .... brain halted

2 1

Re: [Zope-dev] Factory pollution, scopes, zope hosting
by Tres Seaver 13 Jan '00

13 Jan '00

Lalo Martins <lalo(a)webcom.com> wrote: > > > > You have identified a real problem: it is a pain even for me in a site where I > > stage projects for different clients. One solution I had considered was to hack > > the factories to add a "global_visibility" flag to them, and to add a "factory > > proxy" object which would be dropped into the main Zope tree which would > > "surface" its factory to folders which acquired it. > > I thought of this one too, but it would be a major security > problem, because any of your customers with Manager role would > be able to add a ``factory proxy'' (or ``product proxy'') and > gain access to any product you have. Hmm, if the parent of a given user's root folder didn't expose the product, then the user wouldn't be able to either, perhaps? This would mean defaulting to all products available, and then turning them off as folder properties within each branch of the tree where they did not apply. > > I think a scope in the Factory (or perhaps the Product, you > have a good point) is the best sollution. The problem here is that the Product developer won't know how a site manager will want to use the product, in many cases -- or are you suggesting that the site manager might add items to the product folder? -- ========================================================= Tres Seaver tseaver(a)palladion.com 713-523-6582 Palladion Software http://www.palladion.com

2 1

not getting any backtrace on product import
by Stefan Kuzminski 13 Jan '00

13 Jan '00

I'm developing a new product and if there is any error ( syntax or whatever ) when I restart zope, it fails to print anything to let me know what went wrong. The product just isn't in the list of 'Available objects' in the management screen. Is there anyway to get this basic information..? thanks, Stefan Kuzminski

3 2

RE: [Zope-dev] Bug in 2.1.2?
by Jochen Knuth 12 Jan '00

12 Jan '00

Hi, > From: Michel Pelletier <michel(a)digicool.com> > > -----Original Message----- > > From: Robert Sander [mailto:gurubert@gurubert.de] > > Subject: Re: [Zope-dev] Bug in 2.1.2? > > > > > > On Wed, Jan 12, 2000 at 01:39:15PM -0500, Michel Pelletier wrote: > > > Can you also send me your complete Publish.py file? > > > > Attached is the Publish.py > > This is not the Publish.py that comes with Zope 2.1.2. There apears to > be some sort of multi-hosting patch applied to it. The error you are > experiencing is happening in the patch. We didn't write the patch or > know anything about it so there isn't much I can do to help you. > > Did you apply the patch or did debian come with a patched Zope? from the Debian ChangeLog: zope (2.1.2-0.1) unstable; urgency=medium * NMU: new upstream security fix (fixes: #54294, #54086, #54129, #47875, #51820, #53333, #53400) * add README.Subsite-0.6.1 to package (fixes: #45576, #51438) * increase timeout from 30 to 60 seconds (fixes: #45460, #47075) * remove bashims from rules -- Adrian Bridgett <bridgett(a)debian.org> Sat, 8 Jan 2000 19:02:28 +0000 zope (2.0.0-2) unstable; urgency=low * Don't setup an default "access" file upon installation. On upgrade, if postinst finds an access file with the default password, it will purge it for security reasons (closes: Bug#44370: Zope should not use a default superuser password). * lib/python/AccessControl/User.py: apply an upstream fix for an important bug in local roles to lib/python/AccessControl/User.py. * /etc/init.d/zope: a new variable ZOPEOPTS which passes optional arguments to zopectl and then zope-z2 (closes: Bug#44681: zope: zopectl drops arguments and really closes: Bug#43920: zope: doesn't allow -P of zope). Essentially the script now only calls zopectl. * "zopectl start|restart" will now wait until Zope is really up and running. Several other changes to make the operation more smooth. * zpasswd.py: chmod 600 for access. ********** * Applied the Subsite patch 0.6.1 by Andreas Kostyrka <andreas(a)mtg.co.at> (closes: Bug#44991: zope: Bug with virtual hosting (subsiting)) and included README.Subsite-0.6.1. This was not really a bug, but a problem without a solution, and this patch is one solution to this problem. NOTE: If upstream Zope comes up with a better solution, this patch will be removed! *********** There seems to be a problem with Subsite-0.6.1 and Zope 2.1.2 . Ciao, Jochen

1 0

RE: [Zope-dev] Bug in 2.1.2?
by Michel Pelletier 12 Jan '00

12 Jan '00

> -----Original Message----- > From: Robert Sander [mailto:gurubert@gurubert.de] > Sent: Wednesday, January 12, 2000 2:19 PM > To: Michel Pelletier > Subject: Re: [Zope-dev] Bug in 2.1.2? > > > On Wed, Jan 12, 2000 at 01:39:15PM -0500, Michel Pelletier wrote: > > Can you also send me your complete Publish.py file? > > Attached is the Publish.py This is not the Publish.py that comes with Zope 2.1.2. There apears to be some sort of multi-hosting patch applied to it. The error you are experiencing is happening in the patch. We didn't write the patch or know anything about it so there isn't much I can do to help you. Did you apply the patch or did debian come with a patched Zope? -Michel

1 0

RE: [Zope-dev] Bug in 2.1.2?
by Michel Pelletier 12 Jan '00

12 Jan '00

> -----Original Message----- > From: Robert Sander [mailto:gurubert@gurubert.de] If you move your Data.fs file out of the way and let Zope create a new, fresh Data.fs file, does the problem go away? -Michel

1 0

COMMENTS REQUESTED: Zope Product Guidelines
by Martijn Faassen 12 Jan '00

12 Jan '00

Hi there, Monday I posted the Zope product guidelines to the net. It's here: http://www.zope.org/Members/faassen/product_guidelines Structured text source is here: http://www.zope.org/Members/faassen/product_guidelines_stx Don't cheer yet; this document is *not* complete. In fact, it's a mere skeleton, containing (loosely categorized) my questions. I'd like to see some discussion on the various issues raised in the document on this list. I'd also like to see contributions to the doc. Either more questions, or an attempt at actual answers. Since the answers will set guidelines and standards, it's unlikely an answer will be accepted without at least some discussion by the community. So let's please discuss. For starters, let's try to identify some common tabs in Zope, and their use. For instance: edit tab - use this to edit instance specific data that is not a property. (this is incorrect. The title and other properties can often be edited on the edit tab). How to improve this phrasing? properties tab - you can only use this to display the standard Zope properties screen, here's how: from OFS.PropertyManager import PropertyManager # now include PropertyManager as a base class # now include in manage_options {'label':'Properties', 'action':'manage_propertiesForm'}, proxy tab security tab test tab view tab others? Suggested tab orders? Let's get this discussion going! Regards, Martijn

3 3

RE: [Zope-dev] Bug in 2.1.2?
by Michel Pelletier 12 Jan '00

12 Jan '00

> -----Original Message----- > From: Robert Sander [mailto:gurubert@gurubert.de] > Sent: Wednesday, January 12, 2000 11:37 AM > To: zope-dev(a)zope.org > Subject: Re: [Zope-dev] Bug in 2.1.2? > > > On Wed, Jan 12, 2000 at 11:38:50AM -0500, Michel Pelletier wrote: > > > Hmm... me thinks this has nothing to do then with the code in > > Publish.py, that file has been around for years and is > extremly stable. > > If you can't log in the managment interface, the problem is probably > > something completely different. > > But the problem was a raising TypeError at line 154 of > Publish.py, it was > not catched and therefore Zope stopped. But this only happens to you, and this file hasn't changed since sept. of last year, so it must be something with your setup which is causing a type error to be raised. That error is not caught there because it is not intended to be thrown there in a properly configured Zope, if configuration is your problem. What, exactly, causes the error and can you send a complete traceback? -Michel

1 0

RE: [Zope-dev] mod_pcgi2 version 0.4.0
by Michel Pelletier 12 Jan '00

12 Jan '00

> -----Original Message----- > From: Oleg Broytmann [mailto:phd@phd.russ.ru] > > All items had been approved. I got confirmation emails for > all items. > Last confirmation email was today morning, an hour or two > after I created > and asked to catalog mod_pcgi2-v0.4.0. Can you send me your news item so I can try to reproduce this? -Michel

2 1