Re: [Zope-CMF] Full portal import/export

2005-11-03 Thread Brent Hendricks
On 11/3/05, Rui Gamito <[EMAIL PROTECTED]> wrote: > * Module Products.PluginIndexes.common.UnIndex, line 205, in > insertForwardIndexEntry > AttributeError: _length This looks like a Zope2.7 -> Zope2.8 catalog migation issue. Are you going from 2.7 to 2.8? Brent ___

[Zope-CMF] PATCH: Get CMFCore.exportimport.content working with Archetypes

2005-11-03 Thread Brent Hendricks
The DAVAwareFileAdapter currently passes the file's string content both as BODY and BODYFILE in the FauxDAVRequest. This causes problems in Archetypes' BaseContent.PUT() because it expects BODYFILE to be an actual file object. This patch against CMFCore/trunk uses cStringIO to make a file object

[Zope-CMF] ActionsTool bug on CMFCore trunk

2005-11-05 Thread Brent Hendricks
I believe I have discovered a bug in CMFCore/ActionsTool.py on the trunk. The implementation of getActionObject() which it inherits from ActionProviderBase seems to be expecting self.listActions() to return ActionInformation objects since it calls getCategory() on them. But newly created instance

[Zope-CMF] Removing default from browser:skin layers?

2005-11-07 Thread Brent Hendricks
Tres, I'm having trouble with the change you made today taking 'default' out of the list of layers for the cmf browser:skin in CMFDefault/skin/configure.zcml. It seems to cause the views we'e defined in CMFPlone to no longer be found via the context/@@ lookup in page templates. I added layer="cmf

[Zope-CMF] Five:traversable and PortalContent

2005-11-29 Thread Brent Hendricks
When goldegg was first started, plone had a line like this in configure.zcml: I've noticed that this line causes failures in the CMFCore tests so I'm taking it out of plone. If it's necessary it should probably go in CMFCore anyway, but I'm puzzled by the test failures. On the trunk are you

Re: [Zope-CMF] Five:traversable and PortalContent

2005-11-30 Thread Brent Hendricks
On 11/30/05, Lennart Regebro <[EMAIL PROTECTED]> wrote: > I think it *is* in the core now. I'm not sure it should be, though. The only five:traversable declarations I see in the core now are for the workflow and types tools. > It's there to allow you to make views for objects, and I'm not at all