January 2000 - Zope-Dev

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

Re: [Zope-dev] simple revision control(?) for Data.fs.
by Anthony Baxter 12 Jan '00

12 Jan '00

>>> Evan Gibson wrote > On Wed, Jan 12, 2000 at 12:31:15AM -0500, Pavlos Christoforou wrote: > > Hi Anthony - > > I read a posting once where someone suggested using rsync to do something > > similar. Rsync just transmits the changes between versions and has (the > > newer version) support for network access. > > How well does it handle the differences between packed and unpacked data.fs > files? more to the point: will it allow me to say 'give me the data.fs file as it was at 2000/01/05, 5am'[*] ? The code I've just about finished will do this, and it also only stores deltas between files (unless the md5 changes, or the file shrinks, in which case it writes a full file). I also plan to support gzipping the data files in the repository. Once this is done, I'll be running it 12-hourly here to allow us some recovery to any cases of screwups. Anthony [*] well, 'the last backup before this date'.

4 4

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 10:51 AM > To: zope-dev(a)zope.org > Subject: Re: [Zope-dev] Bug in 2.1.2? > > > > Not catching the TypeError disables the hole ZOPE-System, that was the > problem. I could not even log in to the management-screen... 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. -Michel

2 1

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] > BTW, it seems my news items do not appear on Zope front page. They > stopped after I changed naming scheme from mod_pcgi2_v0.2.0 to > mod_pcgi2-v0.3.0 (underscore to dash). It seems ZCatalog hates dashes, > right? Not in a field index, just in a text index. All other index meta-data about your product should catalog normally. If your news items aren't showing up, it may be because no-one has approved it. I don't know, I'm not on the aprover list. -Michel

2 1

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 10:29 AM > To: zope-dev(a)zope.org > Subject: [Zope-dev] Bug in 2.1.2? > > > Hi! > > I just installed Zope 2.1.2 which comes now with debian potato, and I > think I found a bug that may be corrected in the official version. > > In file .../zope/lib/python/ZPublish/Publish.py line 173: > > except KeyError: > > should say > > except TypeError, KeyError: Hmm.. in the latest CVS there is no specified error type at all after the except, the code I have will catch all exceptions. I'll check the 2.1.2 release, since the CVS is different than what you point out that probably means whatever problem you're having is fixed. -Michel

2 1