The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- CMFSetup: provide non-ascii im- and exports,
[Accepted] http://www.zope.org/Collectors/CMF/292
- CMFSetup doesn't correctly detect
Hi,
I've just produced a proof-of-concept version of CMFDefault where the CMF
produces XML documents, and then these are rendered in the browser (for my
own ease!) with XSL. At the moment, this version supports moving round the
site, viewing content and moving/deleting/clipboard stuff in the
Apologies! Although I had tested adding the configured site via the ZMI
several times (though only on 2.8), the removal of the two lines in
setuphandlers somehow got missed out when I posted the code and patches.
It is true that I didn't try checking out a clean install, applying all the
On 22 Sep 2005, at 11:55, computing project wrote:
Apologies! Although I had tested adding the configured site via
the ZMI several times (though only on 2.8), the removal of the two
lines in setuphandlers somehow got missed out when I posted the
code and patches.
It is true that I
Thanks that has made everything much clearer. I'll make sure I label
clearly what conditions I've tested things under in future: I hadn't
fully appreciated that the head might have different dependencies from
the 1.5 branch, though the possibility seems obvious now you've pointed
it out.
On 22 Sep 2005, at 12:55, pete wrote:
Thanks that has made everything much clearer. I'll make sure I
label clearly what conditions I've tested things under in future: I
hadn't fully appreciated that the head might have different
dependencies from the 1.5 branch, though the possibility
On 21 Sep 2005, at 18:10, yuppie wrote:
I see sporadic import errors caused by circular imports:
snip
While not documented in CMFTopic/DEPENDENCIES.txt, http://
svn.zope.org/CMF/trunk/?rev=38002view=rev added a new dependency
on CMFDefault's SkinnedFolder.
Not sure how to resolve this.
Just noticed another debilitating problem with the new cookie
crumbler setup driven by CMFSetup in both SVN trunk and the 1.5 branch.
Symptom: In a new CMFSetup-created site, no one can log in at all. Ever.
Problem: The CookieCrumbler.__call__ method is being registered as
before traverse
yuppie wrote at 2005-9-21 18:10 +0200:
...
File Products/CMFDefault/Portal.py, line 26, in ?
from Products.CMFTopic import Topic
ImportError: cannot import name Topic
In a similar situation (with Archetypes) something like
import Products.CMFTopic.Topic; Topic =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
Just noticed another debilitating problem with the new cookie crumbler
setup driven by CMFSetup in both SVN trunk and the 1.5 branch.
Symptom: In a new CMFSetup-created site, no one can log in at all. Ever.
Problem: The
10 matches
Mail list logo
