[Zope] ZEXP woes with INSTANCE_HOME'd sites
Etienne Labuschagne
ELabuschane@gmsonline.co.za
Wed, 20 Nov 2002 09:10:57 +0200
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C29063.F95DEEC0
Content-Type: text/plain;
charset="iso-8859-1"
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
------_=_NextPart_001_01C29063.F95DEEC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Zope] ZEXP woes with INSTANCE_HOME'd sites</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Thanks for the response Dieter,</FONT>
</P>
<P><FONT SIZE=3D2>I do not have any Directory View folders, its just a =
plain CMF site, containing some structured text docs and Folders (CMF =
Portal Folders).</FONT></P>
<P><FONT SIZE=3D2>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).</FONT></P>
<P><FONT SIZE=3D2>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.</FONT></P>
<P><FONT SIZE=3D2>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!)</FONT></P>
<P><FONT SIZE=3D2>Regards</FONT>
<BR><FONT SIZE=3D2>Etienne</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Dieter Maurer [<A =
HREF=3D"mailto:dieter@handshake.de">mailto:dieter@handshake.de</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Friday, November 15, 2002 9:54 PM</FONT>
<BR><FONT SIZE=3D2>To: GimsMail</FONT>
<BR><FONT SIZE=3D2>Cc: zope@zope.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Zope] ZEXP woes with INSTANCE_HOME'd =
sites</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>GimsMail writes:</FONT>
<BR><FONT SIZE=3D2> > I have two Zope 2.6 sites (this happens =
with 2.5 too) both running EXACTLY</FONT>
<BR><FONT SIZE=3D2> > the same products and CMF 1.3 the only =
difference being the one Zope is an</FONT>
<BR><FONT SIZE=3D2> > INSTANCE_HOME installation and the other =
a standard Zope installation (both</FONT>
<BR><FONT SIZE=3D2> > in Win2K). I have tested this with =
fresh installs too, just to make sure,</FONT>
<BR><FONT SIZE=3D2> > so I guess it will be repeatable by =
anyone else.</FONT>
<BR><FONT SIZE=3D2> > </FONT>
<BR><FONT SIZE=3D2> > When I export a CMF Site from the one and =
try to import it to the other I</FONT>
<BR><FONT SIZE=3D2> > get broken Portal Folder icons and the =
site does not work (gives a</FONT>
<BR><FONT SIZE=3D2> > tuncUnitID attribute error somewhere in =
the actions box). This happens</FONT>
<BR><FONT SIZE=3D2> > consitently and with Zopes on the same =
machine and different machines, the</FONT>
<BR><FONT SIZE=3D2> > only differentiator being INSTANCE_HOME =
or non-INSTANCE_HOME. This happens</FONT>
<BR><FONT SIZE=3D2> > both ways (INSTANCE_HOME to normal and =
other way round). I am not sure if</FONT>
<BR><FONT SIZE=3D2> > this is only a problem with CMF Sites, =
but have not found this problem with</FONT>
<BR><FONT SIZE=3D2> > other products.</FONT>
<BR><FONT SIZE=3D2>I am not sure, but:</FONT>
</P>
<P><FONT SIZE=3D2> CMF DirectoryView saves the path to the folder =
in a compact way,</FONT>
<BR><FONT SIZE=3D2> i.e. if possible not as absolute file path =
but relative with</FONT>
<BR><FONT SIZE=3D2> respect to either "SOFTWARE_HOME" =
or "INSTANCE_HOME".</FONT>
</P>
<P><FONT SIZE=3D2> This, usually is a good thing, as it allows =
your to move</FONT>
<BR><FONT SIZE=3D2> the complete Zope hierarchy without =
rendering</FONT>
<BR><FONT SIZE=3D2> your DirectoryViews disfunctional.</FONT>
</P>
<P><FONT SIZE=3D2> But, when you have exported a portal with =
INSTANCE_HOME</FONT>
<BR><FONT SIZE=3D2> relative paths and import in one without an =
INSTANCE_HOME,</FONT>
<BR><FONT SIZE=3D2> then the affected DirectoryViews may no =
longer work.</FONT>
</P>
<P><FONT SIZE=3D2> In this case, the affected DirectoryViews =
would appear as</FONT>
<BR><FONT SIZE=3D2> empty. You need to fix their path to make =
them working</FONT>
<BR><FONT SIZE=3D2> again.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Dieter</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C29063.F95DEEC0--