[Zope] ZEXP woes with INSTANCE_HOME'd sites

[Dieter Maurer]

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