On Wed, Sep 24, 2008 at 9:39 AM, Arthus Erea <[EMAIL PROTECTED]> wrote: > > > On Sep 23, 2008, at 7:04 PM, Brendan Borlase wrote: > >> On Wed, Sep 24, 2008 at 3:44 AM, Arthus Erea <[EMAIL PROTECTED]> >> wrote: >>> >>> >>> On Sep 23, 2008, at 8:47 AM, Brendan Borlase wrote: >>> >>>> On Tue, Sep 23, 2008 at 8:29 PM, drzax <[EMAIL PROTECTED]> wrote: >>>>> >>>>> I agree that this is very unintuative and I was more than a little >>>>> confused when I first saw this behaviour. I don't think it's enough >>>>> to >>>>> say to theme authors 'please style unpublished posts >>>>> differently'. I >>>>> strongly feel unpublished posts should not be displayed on the >>>>> front >>>>> end by default. Administrators should have an option to put the >>>>> system >>>>> into some kind of preview mode. A simple get parameter would >>>>> probably >>>>> sufice IMHO. >>>>> >>>> >>>> They certainly shouldn't (seconded!). The front end should only ever >>>> show >>>> published posts - including when logged in - and really, in future, >>>> should >>>> only show one's own posts (perhaps all published for a site admin). >>> >>> I'm confused. Why on earth would it not show all published posts? >>> >>> That seems 1 billion times more confusing. IMHO, we should *never* >>> hide published posts from users–whether in the frontend or backend. >>> >> >> Sorry, I'll make it clearer. Anything published by the same logged in >> user should be visible. Key word is "published" here. > > Are you sure you mean published? > > I can in no way support hiding posts from logged in users which are > visible from logged out visitors! >
What? Where did I say that? This has only ever been a discussion about logged in users viewing draft via main page. I have said zero about non-logged in users. Let me try (again) to make this clear. Logged in users should only see published posts on the main page. Logged in users should not see drafts on the main page. Not logged in users should only see published posts. Not logged in users should not see drafts (period). Really not sure how that is unclear? Sorry, but it seems I am being miss-quoted and I don't really enjoy that too much. ;) I did suggest that ACLs could be used to control how much a logged in user could see (again, in a multi-blog context) so perhaps that lead to the confusion? >> >> >> Ideally (ACLs?) a site admin should be able to see all published posts >> and in a multi-site blog, so should any additional editors - logged in >> users perhaps might see only their own drafts? There is a lot of scope >> to build a good ACL model. > > Why would a user *not* be able to see published posts? It's published, > for crying out loud. Why hide it? > > Frankly, I am dumbfounded that we would consider something so > confusing as hiding published posts from _anyone_. > Again, huh? I said "see own drafts" not "see own published posts". No offence Arthus, but your answers don't make much sense to me. I have not once stated published posts should be hidden. Only drafts, and only in context. Which is pretty much how most CMS platforms tend to handle them - and that is typically based on a great deal of user feedback. I think a plugin that allows people to inject drafts into the 'logged in' user view of the front page is a great idea. But as a 'stock' default, it's going to be atypical against what most people have experienced in the past. Obviously I need to work on my communication skills. :D Best, Brendan. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
