[Zope-CMF] CMF-1.1beta problem - unable to run at all

Shane Hathaway shane@digicool.com
Wed, 13 Jun 2001 11:59:21 -0400


Frank McGeough wrote:
> 
> I apologize if I appear ignorant of Zope. The appearance is just a hint of
> the underlying reality. Any help for this problem?
> 
> I have a new Zope 2.3.2 instance on a Windows 2000 machine. I unpack the CMF
> 1.1beta tarball and copy the products into the product directory. On startup
> I get :
> 
> 2001-06-13T14:27:50 ERROR(200) Zope Couldn't import Products.CMFDecor
> Traceback (innermost last):
>   File D:\PROGRA~1\testSite\lib\python\OFS\Application.py, line 528, in
> import_products
>     (Object: string)
>   File d:\Program Files\testSite\lib\python\Products\CMFDecor\__init__.py,
> line 89, in ?
>   File d:\Program
> Files\testSite\lib\python\Products\CMFDecor\FSPageTemplate.py,
> line 95, in ?
> ImportError: No module named PageTemplates.PageTemplate

CMFDecor isn't in CMF 1.1 beta, is it?  It's not at all ready and it's
not required by CMF.

> and the more benign:
> 
> 2001-06-13T14:27:50 PROBLEM(100) Zope No such file or directory: d:\Program
> File
> s\testSite\lib\python\Products\CMFCalendar\help

I wouldn't worry about that. :-)

> I can get to the management console and the CMF products are there but if I
> add CMF Site I get a site error.
> Traceback (innermost last):
>   File D:\PROGRA~1\EmanuEl\lib\python\ZPublisher\Publish.py, line 223, in
> publish_module
>   File D:\PROGRA~1\EmanuEl\lib\python\ZPublisher\Publish.py, line 187, in
> publish
>   File D:\PROGRA~1\EmanuEl\lib\python\Zope\__init__.py, line 221, in
> zpublisher_exception_hook
>     (Object: Traversable)
>   File D:\PROGRA~1\EmanuEl\lib\python\ZPublisher\Publish.py, line 171, in
> publish
>   File D:\PROGRA~1\EmanuEl\lib\python\ZPublisher\mapply.py, line 160, in
> mapply
>     (Object: finish_portal_construction)
>   File D:\PROGRA~1\EmanuEl\lib\python\ZPublisher\Publish.py, line 112, in
> call_object
>     (Object: finish_portal_construction)
>   File d:\Program Files\EmanuEl\lib\python\Products\CMFCore\FSDTMLMethod.py,
> line 180, in __call__
>     (Object: finish_portal_construction)
>   File D:\PROGRA~1\EmanuEl\lib\python\DocumentTemplate\DT_String.py, line
> 538, in __call__
>     (Object: finish_portal_construction)
>   File d:\Program Files\EmanuEl\lib\python\Products\CMFCore\FSDTMLMethod.py,
> line 175, in __call__
>     (Object: standard_html_header)
>   File D:\PROGRA~1\EmanuEl\lib\python\DocumentTemplate\DT_String.py, line
> 538, in __call__
>     (Object: standard_html_header)
>   File D:\PROGRA~1\EmanuEl\lib\python\DocumentTemplate\DT_With.py, line 146,
> in render
>     (Object: stylesheet_properties)
>   File D:\PROGRA~1\EmanuEl\lib\python\DocumentTemplate\DT_Var.py, line 276,
> in render
>     (Object: base_font_color)
> KeyError: base_font_color

base_font_color was accidentally added to the beta.  Andrew Sawyers had
a fix.

"The other problem is that I introduced a bug for the no css skin,
adding
base_font_color to the body tag; this has been backed out of the cvs. 
If
you use cvs, update your sandbox.  If you don't use cvs, you can go to
the
CMFDefault/skins/generic folder, and apply the following patch to
standard_html_header.dtml:"

16,18c16
< <dtml-with stylesheet_properties>
< <body test="&dtml-base_font_color;">
< </dtml-with>
---
> <body>



Shane