The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
mhammond
- Windows DevelopmentMode penalty in CMFCore.DirectoryView,
[Accepted] http://www.zope.org/Collectors/CMF/366
Pending / Deferred Issues
Hi Maurits!
Maurits van Rees wrote:
So here are some points, with suggested changes to the _initIndexes
function in exportimport.py. The tests even run after this, so it
seems these changes do not break anything. But I have not *added*
tests for this.
To get your patches accepted it would
Summary of messages to the cmf-tests list.
Period Thu Mar 1 12:00:00 2007 UTC to Fri Mar 2 12:00:00 2007 UTC.
There were 9 messages: 9 from CMF Unit Tests.
Tests passed OK
---
Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux
From: CMF Unit Tests
Date: Thu Mar 1 21:42:43 EST
Jens Vagelpohl wrote:
I'm working on the second step, trying to effect the component
registration, and keep running into a strange problem. Using the ZMI, I
can get a CMF site created in CMF 1.6 to a functioning state using the
setup tool and executing the following steps + dependencies:
- -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Mar 2007, at 13:36, yuppie wrote:
I can't seem to replicate this in a script. Changing the import
context to CMFDefault:default does not seem to update the
available import steps - however, using the ZMI and the
Properties tab on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2 Mar 2007, at 13:01, Jens Vagelpohl wrote:
I can't seem to replicate this in a script. Changing the import
context to CMFDefault:default does not seem to update the
available import steps - however, using the ZMI and the
Properties tab on
