From c800c78dd75385baf21ce856ffd79052ee331e61 Mon Sep 17 00:00:00 2001 From: Martin Blapp Date: Wed, 13 Feb 2002 21:40:08 +0000 Subject: Add some notes about http.conf and what the user has to do after installation. Noted by: Scot W. Hetzel --- www/mod_frontpage/pkg-message | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'www') diff --git a/www/mod_frontpage/pkg-message b/www/mod_frontpage/pkg-message index 50b2a7ed0611..2fab9e381064 100644 --- a/www/mod_frontpage/pkg-message +++ b/www/mod_frontpage/pkg-message @@ -1,5 +1,20 @@ ************************************************************************ +Check your httpd.conf, if you have included a ResourceConfig and +AccessConfig. If you do not have these files, you'll have to add +these lines to make frontpage extensions working properly: + +ResourceConfig /dev/null +AccessConfig /dev/null + + +You'll also need to change AllowOverride under + ( or the place where you +moved your webservers ) from None to at least: + +AllowOverride AuthConfig Limit Indexes Options + + You can turn off/on the extensions and the frontpage administration per site in httpd.conf and per virtual server. FrontPageAdminDisable is the default if no option is given. @@ -9,4 +24,9 @@ FrontPageDisable # Disable Frontpage Extensions FrontPageAdminEnable # Enable Frontpage Extensions fpadmcgi.exe FrontPageAdminDisable # Disable Frontpage Extensions fpadmcgi.exe + +After you have made these changes, you'll have to execute: + +/usr/local/frontpage/version5.0/fp_install.sh + ************************************************************************ -- cgit v1.2.3