kid at kendermedia
Feb 24, 2000, 12:10 PM
Post #2 of 2
(91 views)
Permalink
|
----- Original Message -----
From: "Mike Pelletier" <mike [at] digicool>
To: <zope-ptk [at] zope>
Sent: Thursday, February 24, 2000 1:19 PM
Subject: [Zope-PTK] DemoPortal.zexp updated
> Jim Fulton passed word along to me that placing a folder in a ZClass
> is a dangerous thing to do, and can lead to undefined behaviour. I had a
> folder called 'Interfaces' in the Portal ZClass. I hoped that by changing
> this, the odd problem of needing to restart after importing a ZClass would
> go away, but alas, nom the probelm lives on. Suggestions would be
> appreciated! This is quite nasty.
I've been working on an updated version of KM|Net News (not a portal version
yet, but probably the last non-portal aware update). I found that when I
imported the new version from my development environment to the real server,
the ZClass instances contained within my main ZClass were broken until I
restarted. I have no idea why this is, but there may be a clue in the fact
that the main ZClass instance (a KMArticleStore) was just fine but the
KMYear instance underneath was broken.
Kevin
|
