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 all,
Is there a generally accepted rule for what generic setup (or a GS
profile, please pardon some possibly shaky terminology) is supposed to
do in case you have an existing list of things? As an example, take
the skins.xml. That's one of the better ones. You have add-before
and add-after or
Summary of messages to the cmf-tests list.
Period Sun Mar 4 12:00:00 2007 UTC to Mon Mar 5 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: Sun Mar 4 21:39:04 EST
On Mar 5, 1:42 pm, yuppie [EMAIL PROTECTED] wrote:
Disclaimer: I believe that the current way extension profiles are
implemented has some fundamental issues,
see:http://mail.zope.org/pipermail/zope-cmf/2006-July/024665.html
Ok, that took 30 minutes out of my day :-)
Are you aware of this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Mitchell wrote:
Looking at the changes rocky made, I don't see why allowing external
methods from non-Products should require making the whole process
completely dynamic on every call. The old mechanism of storing the
product list should be
Hi,
Jens Vagelpohl wrote:
My checkins today addressed at least the second change set you list by
making the site itself a utility and looking it up that way. The
additional wrapping is gone as well.
I tested the branch again against the current Plone trunk and found no
branch related
Previously Hanno Schlichting wrote:
Jens Vagelpohl wrote:
My checkins today addressed at least the second change set you list by
making the site itself a utility and looking it up that way. The
additional wrapping is gone as well.
I tested the branch again against the current Plone trunk
