I have to say that having got another error installing another different product last night (CMFBoard) I saw what you mean by a 'traceback' - I did not get that 'traceback' when I got the error on creating a LocalFS object (and there was nothing in the error log at the root of my ZMI). Should I get such a traceback with *every* error - the rest of the error looked similar, except minus the traceback? Is there something I need to set up in order to be certain that I will? And how do I get it to drop a copy of it into the error_log? Sorry if these are naive questions. But the only way I can report the 'gibberish' is if I can actually see it! Jock On 23 Mar 2004, at 10:49, Samir Mishra wrote:
I've had some other weird behaviour with LocalFS, I'll investigate a bit further, see if the problem is mine, platform related, Zope related or LocalFS related. And post on this list whatever I come up with.
Chris, thanks for you help, and next time I'll provide error logs, trace logs etc. instead of just "gibberish".
Samir.
-----Original Message----- From: Chris Withers [mailto:lists@simplistix.co.uk] Sent: Monday, March 22, 2004 19:45
Samir Mishra wrote:
When I add a LocalFS object and specify the path as "." (ie, current directory), LocalFS doesn't map it to the $INSTANCE/var directory any longer, and neither does it map it to $ZOPE. It's mapped to ..\$ZOPE. This doesn't seem safe either. It's a bother since I've always used relative paths for LocalFS.
I'm not sure relative paths have ever been sane with LocalFS, although they may have worked by chance in the past ;-)
Error Type: AttributeError Error Value: _fs_read
Okay, we have a type and value. Where's the traceback?!
cheers,
Chris -- Jock Coats, in a personal capacity. Wardens Lodgings, J1e, Morrell Hall, OXFORD OX3 0TU T: +44 1865 485019 M: +44 7769 695767 F: +44 845 1275714