October 2003 - Zope-Dev

New location for Zope Collectors
by Jens Vagelpohl 24 Oct '03

24 Oct '03

Hi everyone, The issue collectors formerly hosted on collector.zope.org have been migrated to the main zope.org website and are now available at the following address:: http://www.zope.org/Collectors/ I have tried to find all links to these collectors, but there might be old links in various places that still point to collector.zope.org. The hostname collector.zope.org will, once the DNS change has propagated, point to www.zope.org. jens

4 7

Non-webdav calls on the source port
by Lennart Regebro 23 Oct '03

23 Oct '03

With Zope 2.6, you get an unhelpful error message about manage_FTPget not existing. With the changes I have just checked in, you now instead get an attribute error for most objects. (If the object does not inherit from webdav.Resource you still get an not found message). Nobody is relying on the specific error emssage, right? Should we change it some something HELPFUL? :p //Lennart

1 0

cvs.zope.org down
by Jens Vagelpohl 23 Oct '03

23 Oct '03

Just a quick heads-up: This morning we noticed some odd activity on cvs.zope.org that looked like someone had broken into the machine. We have shut the machine down completely and are in the process of installing new drives and doing a fresh install from the ground up. Then we will start restoring the data from the old drives. We're trying to get at least the basic services (ViewCVS site, CVS anonymous pserver access) up and running by tonight. Migrating the privileged user information to allow checkins will probably be done tomorrow. The collector.zope.org web site, which was served from the same machine, will probably end up being integrated into www.zope.org tomorrow and cease to exist as a separate Zope instance. jens

5 4

manage_workspace changes
by Yuppie 22 Oct '03

22 Oct '03

Hi! As also mentioned here <http://mail.zope.org/pipermail/cmf-checkins/2003-October/003702.html> some CMF tool tabs are broken if used with a current Zope-2_6-branch checkout. I didn't spend much time to find out what's really going on here, so I might be missing something. But it looks like the fix for <http://collector.zope.org/Zope/1058> (regarding an PropertySheets issue) causes this bug. Can anybody confirm this? Or has anybody an other idea which recent change could cause the problem? Was it really necessary to break backwards compatibility? Thanks, Yuppie

4 6

Zope and chunked Transfer-Encoding problem
by Anton Zubenko 21 Oct '03

21 Oct '03

Hello ppl, Could anyone tell me whether Zope 2.5.1 supports Transfer-Encoding: chunked feauture of HTTP/1.1 for handling client request, such as sending a decent amount of data, e.g. file upload? I get Bad Request error with response code 400. I am pretty confident about the request correctness itself. Thanks, A.Z.

2 1

Reminder: bug day tomorrow Oct 21
by Brian Lloyd 20 Oct '03

20 Oct '03

Hi all - A quick reminder that we'll be having a bug day tomorrow 10/21 to try to knock out some remaining issues in the drive to get a Zope 2.7 final out. Hope to see you on #zope-bugday ! Brian Lloyd brian(a)zope.com V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com

3 3

__before_publishing_traverse__ problem (2 args only)
by Tobias Herp 20 Oct '03

20 Oct '03

Hi, I have a Python product which defines a __before_publishing_traverse_ method. At last I thought it would all work fine now... Now I added one of my User Folder objects and got an exception because __before_publishing_traverse__ was called with only two arguments instead of three. Quite curious (because of course I don't call this method myself) I had a look at ZPublisher/BaseRequest.py, line 251, and noticed it is called there without providing the REQUEST. When I monkeypatched this method to hand over the request as the third argument, Zope complained that the "global name 'UNSPECIFIED_ROLES'" was not defined (and nothing worked anywhere anymore). So should I make the REQUEST an _optional_ argument to my __before_publishing_traverse__ method? But the purpose of my b.p.t. method is to remove up to two path elements from REQUEST['TraversalRequestNameStack'] and set request variables appropriately, so what is the purpose of this call in BaseRequest? Is there an article anywhere which explains the whole topic in an understandable way? Thanks, Tobias (Zope 2.6.2,

2 1

Making Zope accept international characters in Id's
by Lennart Regebro 20 Oct '03

20 Oct '03

Hiya everyone! I didn't get any response on my last post, so I'm charging ahead full speed. The fact that litmus complains about Zope's inability to accept UTF-8 filenames is something I view as a bug. It can be fixed simply by changing the default _checkid() implementation to allow extended characters. However, I don't want to break anything, so I think it should be optional, controlled by a setting. Either the already existing, but seemingly undocumented setting management_page_charset could be used to check that the given Id is acceptable in that charset. OR, a separate setting could be used, maybe allowed_id_charset? I'm gonna go with that last one if nobody complains. Suggested code (only the important parts): # Any other characters that should NEVER be allowed?bad_id=re.compile(r'[:;/\\]').search def checkValidId(self, id, allow_dup=0): # So should be allow unicode, then? if not id or not isinstance(id, StringType): if isinstance(id, UnicodeType): id = escape(id) raise BadRequestException, ('Empty or invalid id specified', id) # Here is the characterset checking. This works fine, I've tried it. try: charset = getattr(self, 'allowed_id_charset', 'ascii') id.decode(charset) except: raise BadRequestException, ( 'The id "%s" is not of the allowed character set (%s).' % \ (escape(id), self.allowed_id_charset)) # And here we check for unallowed special characters. if bad_id(id) is not None: raise BadRequestException, ( 'The id "%s" contains characters illegal in URLs.' % \ escape(id)) # And then comes the rest of the tests, as usual, for aq_ and such. # I won't copy them in in this mail. Opinions?

3 3

Problem with request/HTTP_X_FORWARDED_FOR
by Fernando Martins 19 Oct '03

19 Oct '03

Hello, Sorry for the cross-posting but I've posted before on the zope list without reply. The following looks like to be a bug on the lookup of the request attributes. If request doesn't have the attribute HTTP_X_FORWARDED_FOR, the following TALES expression should return REMOTE_ADDR. In fact, it returns the empty string. <p tal:content="request/HTTP_X_FORWARDED_FOR | request/REMOTE_ADDR"></p> Naturally, the following works ok: <p tal:content="python: request['HTTP_X_FORWARDED_FOR'] or request['REMOTE_ADDR']"></p> Shall I file it as a bug or am I missing something? Cheers, Fernando

1 0

SESSION loosing data when system has multiple users
by Steve Jibson 17 Oct '03

17 Oct '03

We have been using Zope 2.7.0-beta2 and we have been having a bit of trouble with SESSION loosing data when we have more than one user on the system. These problems usually show up as KeyErrors when a particular data element in SESSION cannot be found. If I set the zserver threads to 1 in zope.conf, the problem seems to go away (but the system isn't really usable either). So I assumed it was a thread-safety problem in the SESSION code. I decided to be brave and take a look at the code. To my surprize, I found a test file called stresstestMultiThread.py in the lib/python/Products/Sessions/stresstests directory that seemed to be the exact thing I wanted to test. It wouldn't run without a couple of minor modifications, but once I got it running, with more than three or four threads, the tests fail (never complete). Is this test file still valid? It looks like it hasn't been modified for almost a year now. If it is valid, has anyone looked into getting the tests to pass. I will probably look into it more myself, but before I do, I just want to make sure I'm not headed down a dead-end street. Thanks, Steve P.S. - The tests failed in both the 2.7.0b2-src and the what is currently in cvs.

2 3