Re: [Zope] broken products not indicated after Zope 2.2.5 install
Fred Yankowski writes:
I just installed a full copy of Zope 2.2.5 onto my NT 4.0 SP 6 machine and then copied over my data.fs* files from Zope 2.2.3. Zope 2.2.5 comes up OK after that, but none of the Products in the Control Panel / Products folder is shown as broken, even though I have yet to copy over the dozen or so products that I had added onto Zope 2.2.3. Of course, other objects that depend on those products fail and some of those do display a "broken" icon and state. But why don't the incomplete products themselves get flagged as broken? This may be part of a (small) Zope misfeature.
If exceptions occur during some part of product registration, then Zope appears not to update the product state. I suggest, you activate Zope's logging mechanism (either through an environment variable "STUPID_LOG_FILE=file" or with an equivalent command line argument to "start"). Then restart Zope and look at the log file. If you see exceptions there, file a bug report into the Collector. Dieter
I activated Zope logging as you suggested and restarted Zope, but the logfile does not report any exceptions. It only contains routine startup messages such as "ZServer HTTP server started ...". And the Products list still makes it look like they're all OK, when many are in fact broken by virtue of being completely missing in the lib/python/Products directory. On Wed, Jan 10, 2001 at 07:53:02PM +0100, Dieter Maurer wrote:
Fred Yankowski writes:
I just installed a full copy of Zope 2.2.5 onto my NT 4.0 SP 6 machine and then copied over my data.fs* files from Zope 2.2.3. Zope 2.2.5 comes up OK after that, but none of the Products in the Control Panel / Products folder is shown as broken, even though I have yet to copy over the dozen or so products that I had added onto Zope 2.2.3. Of course, other objects that depend on those products fail and some of those do display a "broken" icon and state. But why don't the incomplete products themselves get flagged as broken? This may be part of a (small) Zope misfeature.
If exceptions occur during some part of product registration, then Zope appears not to update the product state.
I suggest, you activate Zope's logging mechanism (either through an environment variable "STUPID_LOG_FILE=file" or with an equivalent command line argument to "start"). Then restart Zope and look at the log file. If you see exceptions there, file a bug report into the Collector.
-- Fred Yankowski fred@OntoSys.com tel: +1.630.879.1312 Principal Consultant www.OntoSys.com fax: +1.630.879.1370 OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA
Fred Yankowski writes:
I activated Zope logging as you suggested and restarted Zope, but the logfile does not report any exceptions. It only contains routine startup messages such as "ZServer HTTP server started ...".
And the Products list still makes it look like they're all OK, when many are in fact broken by virtue of being completely missing in the lib/python/Products directory. Sorry for the wrong hint!
I fear now, that Zope simply looks for the products that *ARE* available in the "Products" subpackage and does not do anything about other products. If you think, this is a bug, put it into the Collector. Dieter
participants (2)
-
Dieter Maurer -
Fred Yankowski