Thu 15 Aug 2002 02:38:27 PM UTC, original submission:
I get the following error message when starting the latest FLE3 checkout on my Win32 platform:
------
2002-08-15T14:35:29 INFO(0) ZServer PCGI Server started at Thu Aug 15 17:35:29 2
002
Inet socket port: 8090
------
2002-08-15T14:36:08 PROBLEM(100) ZODB Could not import class 'CourseManager' fro
m module 'Products.FLE.CourseManager'
------
2002-08-15T14:36:09 PROBLEM(100) ZODB Could not import class 'UserManager' from
module 'Products.FLE.UserManager'
------------------------------------------------------
After this, at least the Course imoprt fails with:
Error: Bad call
('E:\\Dev\\FLE-DEV\\bin\\lib\\xml\\sax\\expatreader.py', 113, 'feed')
Traceback (innermost last):
File E:\Dev\FLE-DEV\lib\python\ZPublisher\Publish.py, line 150, in publish_module
File E:\Dev\FLE-DEV\lib\python\ZPublisher\Publish.py, line 114, in publish
File E:\Dev\FLE-DEV\lib\python\Zope\__init__.py, line 159, in zpublisher_exception_hook
(Object: courses)
File E:\Dev\FLE-DEV\lib\python\ZPublisher\Publish.py, line 98, in publish
File E:\Dev\FLE-DEV\lib\python\ZPublisher\mapply.py, line 88, in mapply
(Object: import_form_handler)
File E:\Dev\FLE-DEV\lib\python\ZPublisher\Publish.py, line 39, in call_object
(Object: import_form_handler)
File E:\Dev\FLE-DEV\lib\python\Products\Fle\CourseManager.py, line 670, in import_form_handler
(Object: courses)
File E:\Dev\FLE-DEV\lib\python\Products\Fle\ImportExport.py, line 140, in _init_
File E:\Dev\FLE-DEV\lib\python\Products\Fle\ImportExport.py, line 206, in loadZip
File E:\Dev\FLE-DEV\bin\lib\xml\dom\minidom.py, line 915, in parseString
File E:\Dev\FLE-DEV\bin\lib\xml\dom\minidom.py, line 902, in _doparse
(Object: parseString)
File E:\Dev\FLE-DEV\bin\lib\xml\dom\pulldom.py, line 234, in getEvent
File E:\Dev\FLE-DEV\bin\lib\xml\sax\expatreader.py, line 124, in feed
File E:\Dev\FLE-DEV\bin\lib\xml\sax\expatreader.py, line 197, in start_element_ns
File E:\Dev\FLE-DEV\bin\lib\profile.py, line 200, in trace_dispatch_i
File E:\Dev\FLE-DEV\bin\lib\profile.py, line 244, in trace_dispatch_call
Bad call: (see above)
|