[Zope] Moving the Data.fs

[Jørgen Larsen]

Hi,

Okay I fixed the problem ;) 

It was the HTMLFile() function that 'generated' the broken path. The problem
was solved by adding a refresh method to the class (named resource) that had
the path problem and making a python script in ZOPE that traversed through
the tree and calling the refresh method on each resource object.

Ie.

def refresh(self):
  manage_main = HTMLFile('resEdit', globals(),language='English')


Best Regards 
http://jorgen.larsen.name



-----Original Message-----
From: J. Cameron Cooper [mailto:jccooper at jcameroncooper.com] 
Sent: 4. december 2003 03:52
To: Jørgen Larsen
Cc: zope at zope.org
Subject: Re: [Zope] Moving the Data.fs


Jørgen Larsen wrote:

>I'm trying to setup a ZOPE test environment so I can test my ZOPE stuff 
>before it is installed on the production server.
>
>The production environment is running on a Linux box and my test 
>environment is running on a WindowXP machine.
>
>I copied the Data.fs and Data.fs.index from the production env. to my 
>test environment - started the ZOPE server - and everything almost 
>seems okay ;) but...
>
>When I try to edit one of my objects (named: resource) I get this ZOPE
>error: Error Value: [Errno 2] No such file or directory: 
>'/usr/lib/zope/lib/python/Products/Localizer/resEdit.dtml' (this is 
>where the dtml file is located on the linux production env.)
>
>The resEdit.dtml is located at 'C:\Program 
>Files\zopelocalizer\lib\python\Products\Localizer\resEdit.dtml' in my 
>test environment.
>
>How do I fix my the path problem? Do I have to traverse through the 
>tree and change an 'edit path' attribute on my objects? Or?
>  
>
I wouldn't know without looking at the source (and even though I can 
theoretically look at the source, I wouldn't know where to begin without 
a traceback and a version number). I doubt reinstalling the product will 
help, but you can try. Speaking of: I can't find a trace of such a file 
in the Localizer CVS.

The solution to the problem lies in finding out why and where Localizer 
stores an OS-specific path. (It shouldn't do this.) You can look through 
the code yourself, or maybe the author(s) of the product can help you. 
It seems to be pretty well-maintained.

          --jcc
-- 

"My point and period will be throughly wrought,
Or well or ill, as this day's battle's fought."