Re: [pmwiki-users] recognizing read protection

2007-06-08 Thread Patrick R. Michaud
On Thu, Jun 07, 2007 at 11:55:42AM -0500, Tegan Dowling wrote: >On 6/7/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: > > On Thu, Jun 07, 2007 at 11:38:10AM -0400, Ben Wilson wrote: > > Forgive me for not giving enough information, but I believe there's a > > Cookbook recipe that allows you t

Re: [pmwiki-users] recognizing read protection

2007-06-08 Thread Hans
Friday, June 8, 2007, 10:05:21 AM, Jabba Laci wrote: > I tried the code below, but it always displays that the page is read > protected, even if it is not. I don't know what I did wrong. >> (:if expr auth admin && pageattribute read :) >> page has read-protection >> (:if expr auth admin && ! page

Re: [pmwiki-users] recognizing read protection

2007-06-08 Thread Hans
Friday, June 8, 2007, 10:05:21 AM, Jabba Laci wrote: > Most of the pages are public, but some of them are made private. These > private pages have the following line in their source: > name= > passwdread=# here! > So what I want to catch is: if the page is read protect

Re: [pmwiki-users] recognizing read protection

2007-06-08 Thread Jabba Laci
Hi, I'll try to give some more details. All my pages are write protected, so I have the following lines in my config.php: $DefaultPasswords['admin'] = ... $DefaultPasswords['edit'] = ... Most of the pages are public, but some of them are made private. These private pages have the following line

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Tegan Dowling
On 6/7/07, Sandy <[EMAIL PROTECTED]> wrote: Tegan Dowling wrote: > I can't speak for Laszlo for sure -- but I know what he asked for > resembles what I want: does this page have a read-attribute set? > > Because if this page does not have a read attribute set (not on the > page's ?action=attr n

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Sandy
Tegan Dowling wrote: > I can't speak for Laszlo for sure -- but I know what he asked for > resembles what I want: does this page have a read-attribute set? > > Because if this page does not have a read attribute set (not on the > page's ?action=attr nor inherited from the group's > GroupAttrib

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Tegan Dowling
I can't speak for Laszlo for sure -- but I know what he asked for resembles what I want: does this page have a read-attribute set? Because if this page does not have a read attribute set (not on the page's ?action=attr nor inherited from the group's GroupAttributes?action=attr), then I want to k

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Vince Administration
THere are two. AuthList in the core: http://www.pmwiki.org/wiki/Site/AuthList and the cookbook AuthTable http://www.pmwiki.org/wiki/Cookbook/AuthTable Seeing the list of everything might be more what you want. But what you asked for is I think (:if !auth read :) etc. Vince On Jun 7, 2007, a

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Hladůvka Jiří
I think it's not so simple as you write. The question is "from who is the page read protected?" You can have users groups, members list etc. and assign the protection accordingly. Then the test (:if isPageReadProtected:) says nothing, as you as an admin are entitled to read all. You can use some

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Vince Administration
THere are two. AuthList in the core: http://www.pmwiki.org/wiki/Site/AuthList and the cookbook AuthTable http://www.pmwiki.org/wiki/Cookbook/AuthTable Vince On Jun 7, 2007, at 11:38 AM, Ben Wilson wrote > Forgive me for not giving enough information, but I believe there's a > Cookbook recipe

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Jabba Laci
Hi, Yes, I tried that recipe (AuthList), but it's not exactly what I want. This recipe gives a long list, but it's very difficult to remember which ones should be protected. So I would prefer to see this information on the top of each page. This way it would be much easier to recognize "hey, why i

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Tegan Dowling
On 6/7/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: On Thu, Jun 07, 2007 at 11:38:10AM -0400, Ben Wilson wrote: > Forgive me for not giving enough information, but I believe there's a > Cookbook recipe that allows you to list pages with their permissions. Starting with 2.2.0-beta52 it's in

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Sandy
Patrick R. Michaud wrote: > On Thu, Jun 07, 2007 at 11:38:10AM -0400, Ben Wilson wrote: >> Forgive me for not giving enough information, but I believe there's a >> Cookbook recipe that allows you to list pages with their permissions. > > Starting with 2.2.0-beta52 it's in the core, at the Site.Aut

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Patrick R. Michaud
On Thu, Jun 07, 2007 at 11:38:10AM -0400, Ben Wilson wrote: > Forgive me for not giving enough information, but I believe there's a > Cookbook recipe that allows you to list pages with their permissions. Starting with 2.2.0-beta52 it's in the core, at the Site.AuthList page. (This may change to Si

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Sandy
To see a summary of passwords for each page, try AuthTable http://pmwiki.org/wiki/Cookbook/AuthTable Worth looking at the second version at the bottom as well; the links go directly to the ?action=attr page. Cheers! Sandy Ben Wilson wrote: > Forgive me for not giving enough information, but I

Re: [pmwiki-users] recognizing read protection

2007-06-07 Thread Ben Wilson
Forgive me for not giving enough information, but I believe there's a Cookbook recipe that allows you to list pages with their permissions. Ben Wilson On 6/7/07, Jabba Laci <[EMAIL PROTECTED]> wrote: > Hi, > > I use PmWiki to manage my personal homepage. Some pages that I don't > want to share wi

[pmwiki-users] recognizing read protection

2007-06-07 Thread Jabba Laci
Hi, I use PmWiki to manage my personal homepage. Some pages that I don't want to share with everyone are password protected. The problem is that as more and more pages are created, it is more and more difficult to keep in mind which pages are protected. I would like to do the following. When a pag