Dieter Maurer wrote:
David Hassalevris wrote at 2005-3-6 18:21 -0800:
... But when I go into the ZMI and click the control panel the SOFTWARE_HOME and ZOPE_HOME point to my old plone paths. This is odd because the Plone instance is disabled as a service.
"SOFTWARE_HOME" and friends are determined in Zope's configuration file (from Zope 2.7 on).
Dieter, Thanks very much for answering. It turns out that the installer was somehow picking up "legacy" paths maybe because I have a separate Python 2.3 already installed. When I started cleaning up my registry of instances of "pythonpath" (and all other old python entries) then python ... sys.path was shrinking ... I first edited \zope-instance\etc\zope.conf and corrected all occurances of the "wrong" zope directories. Re-ran c:\zope-instance\bin\zopeservice but that didnt do the trick. I finally got it to install correctly by editing ZopeService.Py, hard-coding the correct zope_home and software_home and running: "c:\program files\zope-2.7.4-0\bin\python zopeservice.py" --startup auto install. Note: notice the full path to the zope python.exe. Using my "other python 2.3" which in the system path was giving different results. Seems that *anyone* that has prior 2.7x versions installed and is using windows and who has python 2.3 "outside" of Zope\bin will run into this. But then i'm cursed so it could just be me! Thanks again, David