Apart from another issue I've been having with LocalFS, which I think I may have fixed by upgrading LocalFS to ver. 1.1, I'm experiencing other unexpected behaviour. 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. And when I try and edit (and only on edit) the path on an already existing LocalFS object from the Properties tab, I get the following error - =============== Site Error An error was encountered while publishing this resource. Error Type: AttributeError Error Value: _fs_read Troubleshooting Suggestions * The URL may be incorrect. * The parameters passed to this resource may be incorrect. * A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the error log. If the error persists please contact the site maintainer. Thank you for your patience. =============== Any way to fix this? Using Python 2.3.3/Zope 2.7/LocalFS 1.1 Thanks. Samir
I recently wrote a couple of hacks to make LocalFS work for me with Page Templates. Even though I put my patches up on Zope.org, I don't really feel like my quick hacks are worthy of the LocalFS name. Mainly I put it up because it worked for me in Zope 2.6 and I wanted to archive my work :) Local File System is a good product, but we still only have a stable version just under 2 years old which is not keeping up with Zope development. What do other people think about the development (or lack of) of this product? Do you see it as an important product? What are people's experiences with the CVS version 1.1?
I am categorically not an expert, and after my last post on this issue you'll know why I am keen, but I'd have thought it was quite a useful thing to be able to offer - access to controlled areas of the file system - one fewer protocols and daemons to have to manage and take care of. And possibly essential in a document management type system. I'd love to help, but though I can read Python, very slowly with a book in the other hand, I have not got my head round how things work in Zope to be of much use developing just now. Jock On 16 Mar 2004, at 22:53, Chris Beaven wrote:
I recently wrote a couple of hacks to make LocalFS work for me with Page Templates. Even though I put my patches up on Zope.org, I don't really feel like my quick hacks are worthy of the LocalFS name. Mainly I put it up because it worked for me in Zope 2.6 and I wanted to archive my work :)
Local File System is a good product, but we still only have a stable version just under 2 years old which is not keeping up with Zope development. What do other people think about the development (or lack of) of this product? Do you see it as an important product?
What are people's experiences with the CVS version 1.1?
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-- J1e Morrell Hall, OXFORD, OX3 0BP, United Kingdom T: +44 1865 485019 F: +44 845 1275714 M: +44 7769 695767
participants (3)
-
Chris Beaven -
Jock Coats -
Samir Mishra