Thanks for the response Dieter, I do not have any Directory View folders, its just a plain CMF site, containing some structured text docs and Folders (CMF Portal Folders). The Folders' icons are broken, even though you can still get into them. When trying to view the portal, I get the error (see the traceback that I posted on p.t.'s request). I can even replicate this consitently with two brand new installations AND brand new CMF sites on any machine. Create a new CMF site, add a Portal Folder, export the site, import it in the other site. The only difference with a new CMF site is that I don't get the error when viewing the imported folder, I only get the standard Zope intro screen instead of the portal rendering. The only difference between the two sites is that one is a instance home'd site and the other is not. I'm quite sure that anyone else should be able to replicate this (on Win32 at least). I don't know if I must rather put this issue in the collector (I need to be sure I'm not doing anything stupid first!) Regards Etienne -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Friday, November 15, 2002 9:54 PM To: GimsMail Cc: zope@zope.org Subject: Re: [Zope] ZEXP woes with INSTANCE_HOME'd sites GimsMail writes:
I have two Zope 2.6 sites (this happens with 2.5 too) both running EXACTLY the same products and CMF 1.3 the only difference being the one Zope is an INSTANCE_HOME installation and the other a standard Zope installation (both in Win2K). I have tested this with fresh installs too, just to make sure, so I guess it will be repeatable by anyone else.
When I export a CMF Site from the one and try to import it to the other I get broken Portal Folder icons and the site does not work (gives a tuncUnitID attribute error somewhere in the actions box). This happens consitently and with Zopes on the same machine and different machines, the only differentiator being INSTANCE_HOME or non-INSTANCE_HOME. This happens both ways (INSTANCE_HOME to normal and other way round). I am not sure if this is only a problem with CMF Sites, but have not found this problem with other products. I am not sure, but:
CMF DirectoryView saves the path to the folder in a compact way, i.e. if possible not as absolute file path but relative with respect to either "SOFTWARE_HOME" or "INSTANCE_HOME". This, usually is a good thing, as it allows your to move the complete Zope hierarchy without rendering your DirectoryViews disfunctional. But, when you have exported a portal with INSTANCE_HOME relative paths and import in one without an INSTANCE_HOME, then the affected DirectoryViews may no longer work. In this case, the affected DirectoryViews would appear as empty. You need to fix their path to make them working again. Dieter