Etria Lists

Tim Hicks wrote:
> Raphael Ritz wrote:
> 
>> Other than that, I personally would not like yet another configlet to
>> (re)map workflow states to what the blog should consider public
>> versus draft etc. I think it is better to honor the existing
>> settings. Alternatively, one could consider using a custom
>> (or local to the blog) workflow from the onset.
> 
> For the purposes of implementing methods like IWeblog.getDrafts(), how 
> would we distinguish between drafts and published items when a user has, 
> say, the Manager role?
> 

Ah, OK, now I think I see the problem. Sorry for not thinking
about this more carefully before chiming in.
It seems to be tricky indeed in particular in the context
of QuillsEnabled.

Again, just thinking out loud: would it help to consider the
option of having a BloggingWorkflow in addition to the regular
workflows - I mean such that objects that are marked as blog
entries become subject to an additional workflow managing a
'blogging_state'. That way it would be possible to combine
any existing workflow with the blogging workflow and states
could be managed independently.

Just an idea.

(should anyone be interested in this approach: my LockingWorkflow
- available from plone.org - works similar and could serve as
an example of how to do that)

>> In the long run - by which I mean supporting arbitrary content
>> as blog posts - I think the only way to avoid confusion will be
>> to control general access and modification rights in the general
>> Plone (aka workflow) way and let the assignment of a marker interface
>> plus appropriate adapter (or whatever the idea is) determine what's
>> part of the blog.
> 
> Unless I'm misunderstanding you, that's the way things are for 
> QuillsEnabled right now - once I get it working again.
> 

Any specific problem there? - I mean other than lack of time ;-)

Raphael


> 
> Tim