[Zope] ZopeTestCase and INSTANCE_HOME

[Stefan H. Holek]

Sandor,

This is no longer a problem with CMF 1.4 DirectoryViews, so I assume 
FileSystemSite has not been updated yet.

Anyway, the changing of INSTANCE_HOME is an artefact of importing the 
Testing package. There are ways to work around it though. Here's how I do 
it (see class TestImportExport):
<http://cvs.sourceforge.net/viewcvs.py/collective/ZopeTestCase/testZODBComp
at.py?rev=1.14&view=auto>

Still, the IMO better solution is to update FSS or have a look at 
Standalone Skins: <http://www.plope.org/Members/chrism/standalone_skins>

HTH,
Stefan


--On Freitag, 05. März 2004 15:14 -0600 zope at netchan.cotse.net wrote:

> I use the FileSystemSite product
> (http://www.zope.org/Members/k_vertigo/Products/FileSystemSite) to serve
> some static pages for the management pages of my product. If your static
> content folder is under INSTANCE_HOME, FSS trims this prefix from the
> path
> (http://cvs.infrae.com/FileSystemSite/utils.py?rev=1.1&content-type=text
> /vnd.viewcvs-markup - minimalpath method).
> This means that the path you have to pass to createDirectoryView depends
> on if your INSTANCE_HOME points to the home of your product or not.
> A workaround for this is to check if INSTANCE_HOME really points to your
> instance and set the filepath argument of createDirectoryView
> (http://cvs.infrae.com/FileSystemSite/DirectoryView.py?rev=1.5&content-t
> ype=text/vnd.viewcvs-markup) accrodingly, however this is a hack and I
> hate hacks ;-)
>
> Regards,
> Sandor
>
--
The time has come to start talking about whether the emperor is as well
dressed as we are supposed to think he is.               /Pete McBreen/