• Wicked List

  • wicked question

    from "Wohnlich, Eric \(IMS\)" on Jan 09, 2008 05:20 PM
    I was not able to find any documentation on making new content types
    (besides documents, events, and news items) registered with Wicked. For
    instance, I have a content type that subclasses ATDocument and would
    like to make it wiki-aware. I dug through the code and it looks like
    those types are set up in wicked.plone.registration.py but surely that
    is not intended to be modified to allow new content types! Is there some
    lines I can add to my product's configure.zcml file (I'm using Plone
    3.0.4 btw) to make my type wiki-aware and registered as a
    WikedPortalType?  Any help appreciated.
     
    Thanks,
    Eric
     
     
    --------------------------------------------------------
    
    Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
    
    
    Thread Outline:
  • Re: wicked question

    from whit on Jan 10, 2008 09:43 AM
    On Jan 9, 2008 4:18 PM, Wohnlich, Eric (IMS) <WohnlichE@...> wrote:
    
    >  I was not able to find any documentation on making new content types
    > (besides documents, events, and news items) registered with Wicked. For
    > instance, I have a content type that subclasses ATDocument and would like to
    > make it wiki-aware. I dug through the code and it looks like those types are
    > set up in wicked.plone.registration.py but surely that is not intended to
    > be modified to allow new content types! Is there some lines I can add to my
    > product's configure.zcml file (I'm using Plone 3.0.4 btw) to make my type
    > wiki-aware and registered as a WikedPortalType?  Any help appreciated.
    >
    > Thanks,
    > Eric
    >
    
    if you are using a subclass of ATDocument and turn on wiki behavior for
    pages, it may just work. Essentially, there is a directive that marks the
    field you want to be wiki enabled, then an interface for the content object
    itself.  With sublclasses, I think this should all be working, but let me
    know if it doesn't and I'll help you with a solution.
    
    -w
    
    
    >
    >
    >  ------------------------------
    >  Information in this e-mail may be confidential. It is intended only for
    > the addressee(s) identified above. If you are not the addressee(s), or an
    > employee or agent of the addressee(s), please note that any dissemination,
    > distribution, or copying of this communication is strictly prohibited. If
    > you have received this e-mail in error, please notify the sender of the
    > error.
    >
    
    
    
    -- 
    
    | david "whit" morriss
    |
    | contact :: http://public.xdi.org/=whit
    
    "If you don't know where you are,
     you don't know anything at all"
    
     Dr. Edgar Spencer, Ph.D., 1995
    
    
    "I like to write code like
    other ppl like to tune their
    cars or 10kW hifi equipment..."
    
    Christian Heimes, 2004