Re: [Plone-UI] Re: Making the contents tab consistent - a solution

On Monday 27 June 2005 05:20 am, Florian Schulze wrote:
> On Mon, 27 Jun 2005 10:42:43 +0200, Danny Bloemendaal
>
> <danny.bloemendaal-YihP0OB+nP1UH/[email protected]> wrote:
> > I think this is a good idea. It makes it a bit more cumbersome to get
> > the parent-folder's contents view but that's ok.
> >
> > One thing I want to mention though is that the reason to open
> > folder_contents is not only to do batch processing. Many products have
> > another default view (like blogs) and in these cases, the only way to
> > see what is in a folder is to open it in contents view. In the blog for
> > instance, the default view only shows published items. Items in draft
> > are inaccessible without contents view. Just my two cents ;-)
> >
> > Danny
>
> That's a problem in the default view of those products IMO, when you have
> the right to see such entries then you should be able to see them, maybe
> with some mark that they aren't published or something. This should be
> documented in a tutorial like "How to write good products for Plone" (we
> could start with a simple FAQ).

Yes, listings like this should use permissions not directly testing workflow 
state.  Otherwise, you allow users to see the unpublished content, while just 
not telling them about it, and making it inconvenient for those who have 
permission to view these things to ever see them.  Of course, the default 
Plone workflows provide a somewhat bad example in this regard.

Alec


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click