Previously Jens Vagelpohl wrote:
> On Nov 16, 2008, at 22:30 , Wichert Akkerman wrote:
> > Previously yuppie wrote:
> >> I don't like to remove CMF's portal_setup registration *if* CMF
> >> itself
> >> is not affected by this issue.
> > Imho registering portal_setup as a utility as long as any CMF tool
> > uses
> > self.REQUEST is problematic since it makes it impossible for
> > import/export steps to use such tools.
> I suggest we *look* at the current CMF situation before acting on the
> assumption that non-utility tools are used in (and break) CMF import/
> export steps. It's been working fine so far.
I'm sure CMF import/export steps are fine. The CMF tools are not, and
third party products use those in their steps. That is exactly the
problem we where seeing in Plone, and which is why I removed the utility
Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests