[pmwiki-users] Display error message when an include fails

[H. Fox]

On 1/27/06, Patrick R. Michaud <pmichaud at pobox.com> wrote:
> On Fri, Jan 27, 2006 at 04:57:42PM -0600, JB wrote:
> >
> > Admins who do not want error messages could turn
> > this off. If they are smart enough to not need/use
> > an error message, then they are smart enough to
> > turn this off in the local/config.php file.
>
> But admins (and authors) will also be surprised and confused
> when (:include:) statements suddenly start revealing the existence
> of pages that are supposed to be "read protected" and therefore
> hidden from view.  This isn't idle speculation, it's a fact
> demonstrated many times over on this mailing list.  It was
> such a common complaint that for 2.1 we've changed the
> default for $EnablePageListProtect to be "on" (previously
> it was "off").
>
> It's not a question of admins being smart enough to change
> the configuration (administrators could've easily set
> $EnablePageListProtect=1 in config.php) -- it's a question
> of "principle of least surprise" with the defaults.

Here, here.

> One other possibility is that we have (:include:) honor the
> setting of $EnablePageListProtect, so that it keeps quiet
> if someone attempts to include a read-only page.

Read-only or read-protected?

>  But even
> in this case, the default out-of-the-box configuration would
> end up being "display nothing".

It's doubtful anyone would want such an error to appear on a page the
visitor isn't authorized to edit, so some sort of test for
edit-authorization might be helpful.

Hagan