[pmwiki-users] SiteAdmin.SiteAttributes

[Patrick R. Michaud]

On Sat, Jun 23, 2007 at 04:34:48PM +0200, Petko Yotov wrote:
> On Thursday 21 June 2007, Dominique Faure wrote:
> > On 6/21/07, Petko Yotov <5ko at free.fr> wrote:
> > > Is there a way to have a special page Site.SiteAttributes like
> > > Group.GroupAttributes, but for the whole site?
> > >
> > > Like: if one sets a read/edit password, or @lock on this page, the whole
> > > site gets closed. Groups or Pages with the @nopass attribute will be
> > > visible, that is, their attributes override the Site.SiteAttributes
> > > settings.
> ...
> > BTW, this could be a perfect place to have some other global settings
> > (for now only set via config.php), such as the $WikiTitle variable,
> > no?
> 
> Actually, when Patrick doesn't reply, it is almost certain that what we beg 
> for can be done quite simply with a recipe.

Actually, it's just generally true that most things can be done with
a recipe.  :-)

As far as my response time is concered, my replies are quite a bit
slower than usual this week because I'm preparing to attend 
(and present) at the YAPC::NA conference next week, so that's
limiting the time I have available for answering emails and
working on PmWiki.

> Here is something that does all this. Patrick, can you please look at this 
> code to see if it is not dangerous of some kind? Or if it may be 
> optimized/simplified?

I haven't been able to look at it closely -- the bit about loading
the passwords looks okay to me.  The $GroupTitle page variable will not
always do what you expect, especially if one tries to use it in
pagelists or includes.

> Note that this code should probably be placed *after* any PageStore 
> definition (per-group-sub-directories), after UTF-8 (xlpage-utf-8.php, 
> XLPage())

Definitely. If there's a strong demand for being able to configure
PmWiki features via a wikipage, we can see about developing a more
complete recipe for it.  What features should be configurable?

Pm