Michel Pelletier <michel@digicool.com> writes:

The problem is XEmacs. It first deletes the file and saves a backup '~', and then an original. Because it deletes the origninal object instead of overwriting it, Zope assumes that the *new* file is to be a document. I bet a gazzillion dollars that there is some lisp variable somewhere in EFS to disable this behavior.

The variable is 'efs-make-backup-files', which is a list of host types (efs has a concept of host type and will do different things when talking to VMS, say, than when talking to Unix) on which to make backup files when saving. If you set it to 'nil' efs will never make a backup file on a remote machine. If you want to make backup files on 'real' ftp servers but not on Zope's, this could be a problem, as 'efs-process-host-type' is "unix" when connected to a Zope server, just as it is with normal systems. I don't know whether there might be a way to make Zope recognizable to efs. I did do a test with setting 'efs-make-backup-files' to nil and doing a few efs edits through localhost (standard ftp server). The inode number of the file in question did not change, indicating that efs just did a 'put' when saving the file, rather than deleting and recreating. Thus from Michel's comments, Zope should do the Right Thing and preserve the document type if you nil out the above variable. Hope this helps. -Doug -- Doug McNaught doug@mcnaught.org http://www.mcnaught.org/~doug