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 To: Samir Mishra Cc: zope@zope.org Subject: Re: [Zope] Newbie Q: Error creating LocalFS 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 -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk