I’ve been using archetypes.schemaextender lately, to extend the Plone Event schema (in an effort to get useable recurring events). And it works. No big problems, and highly recommended.

Only problem: Well, as I understand it, you can really only have one extender per type. This is solvable by letting that type in return look up other “subextenders”, which is what I do, but it would have been nicer if this was supported already.

Update: Wiggy tells me  that you can have multiple extenders if you name them. I’ll try that.

An example of this will pop up in p4a.ploneevent shortly, which is the product that contain the recurring event support.


  1. Florian Schulze

    You *can* have more extenders for each type, that was one of the first reasons for archetypes.schemaextender. You just register several *named* adapters on the same type, where the name itself is arbitrary, but to avoid conflicts you should use a dotted name related to you package name. The old way, where you wrote an adapter for ISchema directly only allowed one adapter.

  2. Roger Erens

    This subject looks very much like extending a blog entry with comments! The only issue remaining is to attribute the correct name to a comment :)

  3. Lennart Regebro

    Actually Wiggy told it to me via IRC, about exactly at the same time as Florian did here on the blog. So I didn’t see Rogers comment until after I edited the page.

Leave a Comment