[Zope-CMF] Moderated Discussion

Chris Withers chrisw@nipltd.com
Thu, 14 Feb 2002 08:40:40 +0000


Is ther eany reason why Squishdot won't suffice in this instance?

cheers,

Chris

Lennon Day-Reynolds wrote:
> 
> I've worked with Zope previously, but am relatively new to the CMF, so
> please forgive any blatant newbie-isms I'm about to throw out there.
> 
> Basically, the project I'm working on requires a moderated discussion
> capability. The workflow tools in the CMF seem like a good fit, but I'm
> struggling with the issue of how best to add a normal workflow process to
> the DiscussionItem type, which normally jumps directly to the "published"
> state.
> 
> I've looked at the Python sources in CMFDefault, and can see a line near
> the top of the DiscussionItem class definition which sets the workflow
> status of new comments to "published" by default. I also can't see any
> additional code which looks as though it would prevent the discussion type
> from being subject to the default workflow policies. However, I wanted to
> do a quick sanity-check with a more experienced group before I started
> hacking sources to do what might be a very simple change.
> 
> My basic plan had been to create a new "Posting" class, which would behave
> more like the standard CMF types, including a "publishing" view method. It
> might even simply inherit from the DiscussionTool class, but block the
> automatic publishing operation, so that user comments would also have to be
> approved by a site moderator.
> 
> Does this sound crazy? Are there any big "gotchas" lurking in the heart of
> the CMF that might make this much more complex than I think?
> 
> Thanks,
> 
> Lennon Day-Reynolds
> lennon@day-reynolds.com
> 
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF@zope.org
> http://lists.zope.org/mailman/listinfo/zope-cmf
> 
> See http://www.zope.org/Products/PTK/Tracker for bug reports and feature requests