[Zope] FrameSet as index_html

[Andy Yates]

Thanks!  I am migrating an existing site to Zope and whoever did the =
original did not include a "head" element on the index page.

-----Original Message-----
From: Dieter Maurer [mailto:dieter@handshake.de]
Sent: Tuesday, July 16, 2002 2:57 PM
To: Andy Yates
Cc: zope@zope.org
Subject: Re: [Zope] FrameSet as index_html


Andy Yates writes:
 > I do not understand the following behavior.  Why is this happening =
and is there a workaround?
 >=20
 > Let's say I have the following structure:
 >=20
 > /foo
 > 	/bar
 > 		index_html
 > 		AFrame_html
 > 		BFrame_html
 >=20
 > index_html is a frame set that includes two frames, AFrame_html and =
BFrame_html.  If I point my browser to /foo/bar/ everything works fine.  =
However, if I leave off the trailing slash and access /foo/bar the frame =
set loads but the two frames show site errors.  One shows "Cannot locate =
object at /foo/AFrame_html" and the other shows "Cannot locate object at =
/foo/BFrame_html." =20
That is a problem with relative URLs.

Zope automatically extends your URL from "/foo/bar" to =
"/foo/bar/index_html".
It tries to inform the browser of this URL change by setting
a "base" tag such that the browser can resolve relative URLs correctly.

Apparently, this does not work. This may have several causes:

  *  your "index_html" has already a "base" tag

  *  your "index_html" does not have a "head" element

  *  your "index_html" is somewhat strange, such that the
     regular expression use to find the "head" element fails.


Dieter