Etria Lists

On Jan 7, 2008 1:11 PM,  <admin at plone.org> wrote:
>
>
>
> A new issue has been submitted to the Issue tracker tracker by T. Kim Nguyen
> and awaits confirmation.
>
> Issue Information Issue does not play nicely with Intranet/Extranet Workflow
> (http://plone.org/products/quills/issues/127)
>
> Issue Details: Quills uses the hardcoded workflow state "published" to
> decide if
> there are any entries in a blog and display them. If I set a
> Plone 3 site to use the intranet/extranet workflow (which uses the
> states private, internal, internally_published, pending,
> external), this leaves all blogs thinking they are empty even
> though they contain entries. The temporary fix to make Quills
> 1.6 work with intranet/extranet workflow is: 1. In the file
> lib/python/quills/app/topic.py change lines 126 and 184 from
> review_state='published') to
> review_state='internally_published') 2. In the same dir, the
> file archive.py, change lines 158 and 303 from
> review_state='published', to
> review_state='internally_published', 3. In the same dir, the
> file weblogentrybrain.py, change line 126 from return
> self['review_state'] == 'published' to return
> self['review_state'] == 'internally_published' 4. Restart the
> Zope server. Ideally Quills would allow an admin to tell it
> which workflow state(s) to consider entries to be 'published', or
> which state(s) to consider an entry to be 'private'. A short term
> fix would be to have Quills assume that any entry with state
> 'private' should be hidden, and an entry with any other state
> should be 'published'.

Why code Quills to workflow states? Why not just have Quills obey the
visibility attributes on the underlying content items according to
standard permissions? Thus viewing a blog post, like viewing content
in other ways, could be managed by workflows written by admins.

This opens up having blogs that display user-specific entries based on
security. That sounds nice, to me.

BTW, this problem is why blogs are borken on my site, but, since all
my workflows are custom, none of the variations on 'hardcode a
workflow name' will work for me.

Derek