• Remember Mailing List

  • membrane with non-AT content types

    from Florian Friesdorf on Mar 10, 2008 02:37 PM 
    Hi all,

I am trying to a custom non-archetype, but plone.app.item.Item derived content
type and to use it as a user. My problem is: it does not get cataloged, whereas
the borg charity example employees do.

Before trying to debug further: does membrane support non-AT content at all?

--
florian
    Thread Outline:

  • Re: membrane with non-AT content types

    from Florian Friesdorf on Mar 13, 2008 07:52 AM 
    On Mon, Mar 10, 2008 at 07:35:53PM +0100, Florian Friesdorf wrote:
> Hi all,
> 
> I am trying to a custom non-archetype, but plone.app.item.Item derived content
> type and to use it as a user. My problem is: it does not get cataloged, whereas
> the borg charity example employees do.
> 
> Before trying to debug further: does membrane support non-AT content at all?

Well, for completeness sake and the next person, searching the same patterns: I
meanwhile found out and jensens confirmed in irc: current membrane does not
support non-AT content types. The membrane_tool is using AT's IReferenceable in
several places and relies on archetype_tool for catalog updates. I am working
towards a solution to use non-AT types as sources of users and groups for
PlonePAS. If anybody is interested in a non-AT membrane or even to help, please
let me know. If I make any progress, I'll post here.

--
florian

    • Re: membrane with non-AT content types

      from ra on Mar 13, 2008 01:08 PM 
      On Mar 13, 2008, at 7:50 AM, Florian Friesdorf wrote:

> On Mon, Mar 10, 2008 at 07:35:53PM +0100, Florian Friesdorf wrote:
>> Hi all,
>>
>> I am trying to a custom non-archetype, but plone.app.item.Item  
>> derived content
>> type and to use it as a user. My problem is: it does not get  
>> cataloged, whereas
>> the borg charity example employees do.
>>
>> Before trying to debug further: does membrane support non-AT  
>> content at all?
>
> Well, for completeness sake and the next person, searching the same  
> patterns: I
> meanwhile found out and jensens confirmed in irc: current membrane  
> does not
> support non-AT content types. The membrane_tool is using AT's  
> IReferenceable in
> several places and relies on archetype_tool for catalog updates.

indeed this is true.  lack of foresight on my part.  :-P

> I am working
> towards a solution to use non-AT types as sources of users and  
> groups for
> PlonePAS. If anybody is interested in a non-AT membrane or even to  
> help, please
> let me know. If I make any progress, I'll post here.

absolutely, very interested in this.  i unfortunately don't have a  
lot of (read: any) time to work on this, but i'm happy to answer  
questions and/or do code review to support your efforts.

note that it'd be nice to still have the current, AT-based behavior  
as a part of what membrane provides.  it's just that currently,  
membrane _assumes_ this is how things will be put together.  instead,  
i think membrane should provide "adapter sets".  one of these adapter  
sets would use AT infrastructure to manage the member data and  
relationships, but other adapter sets could manage this in a way that  
doesn't depend on AT at all.

-r
Return to conversation view