[pmwiki-announce] Re: [Pmwiki-users] Installing 2.0.beta10

Patrick R. Michaud pmichaud
Wed Dec 15 06:44:13 EST 2004

On Wed, Dec 15, 2004 at 11:23:38AM +0100, chr at home.se wrote:
> On Tue, 14 Dec 2004, Patrick R. Michaud wrote:
> > I'd greatly appreciate any testers that could run through a quick,
> > sample "fresh installation" of this latest distribution onto their 
> > server(s) and report back about any bumps in the install process.
> Some comments from when reading PmWiki/Installation
> * It'd be nice if there was a direct link to the latest pmwiki tar-ball.
>   Perhaps create a link in the pub-directory called 'pmwiki-latest.tgz', 
>   and link to that from the wiki page?

There's already such a link in the pub-directory (at least, there was),
but we'd probably need a link to the zip archive as well.  

> Bah... I just did the first step where you browse to pmwiki.php and 
> followed the instructions. Then (as usual..) I did reload and lost the 
> isntructions for how to revert the directory settings... *sigh*

The new procedure provides a link to click for reloading -- if you follow
the link (as opposed to hitting reload), then PmWiki opens in a new 
window so that the instructions for reverting the directory settings 
are still available.  :-)

> How about if pmwiki shows those instructions on the main page as long as 
> some variable isn't set in the configuration file? They could be shown as 
> long as $EnableDiagnostics = 1. Then when the user sets $EnableDiagnostics 
> = 0, this text is no longer shonw.

Nope, I think littering the main page with administrative diagnostics is
probably the wrong way to go.  Better is to make an "analyze setup" 
procedure a part of the InitialSetupTasks.

> Another alternative could be to make the links for reloading pmwiki open 
> in a new window? That way you'd still have the instructions on screen?

See above.  :-)


More information about the pmwiki-announce mailing list