On Sun, May 20, 2007 17:36, Patrick R. Michaud wrote: > On Sun, May 20, 2007 at 05:23:56PM +0200, ThomasP wrote: >> On Sun, May 20, 2007 16:10, Patrick R. Michaud wrote: >> (II): >> > Another approach I could use is that pagelist and other functions >> assume >> > that a page has a password unless $page['=passwd']['read'] is >> explicitly >> > set to an empty string. Then authorization functions that don't set >> > $page['=passwd']['read'] will still work properly (but perhaps reduce >> > the amount of caching that gets performed). >> >> I think (II) makes sense if you also know a solution for >> $page['=auth']['read']. Then really all auth modules will automatically >> work. (Besides of UA2 I know of UserAuth and AuthPhpBB2(?) only.) > > The current structure of things pretty much requires that custom > authorization functions correctly return $page['=auth']['read']. > Otherwise some recipes and other code items that rely on this > simply aren't going to work properly. If that's a big issue we > can see about migrating to something easier to implement, but > as things stand now there are a number of things relying on > $page['=auth']. >
No problem. For UA2 the $page['=auth']['read'] was already on the "done" list, that's easy -- will be something like if (HasCurrentUserPerm($pagename, 'read')) $page['=auth']['read'] = 1; Besides, I will set the $page['=passwd']['read'] to "1". Thomas _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
