Add some notes about http.conf and what the user has to do

after installation.

Noted by:	Scot W. Hetzel <hetzels@westbend.net>

1 files changed, 20 insertions, 0 deletions

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
+<Directory "/usr/local/www/data"> ( 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
+
 ************************************************************************