Nevermind I found the solution for getting past this.
Just tried it and it works.
If you are using an apache server, frontpage, and mod_rewrite your frontpage extensions will stay broke.
To get past this do the following:
Were not allowed to post links here so I will just copy and paste the info from the msfrontpage dot Net site.
______________________________________________________________
The information below was retrieved from msfrontpage [dot] net on June 14th 2005.
Apache Rewrite Engine and FrontPage
1. Pro
You can use the Apache Rewrite engine with FrontPage Server Extensions.
2. Con
After you made the required modifications (see below), no FrontPage user will be able to create a new subweb on demand.
They must first create the subweb; they will get an error message.
Then you will have to update the .htaccess files (see below) in the new subweb before FrontPage Explorer can talk to the new subweb.
STEPS
A. Modify the root web .htaccess file with notepad or another text editor; FTP is done in ASCII mode in all cases.
Example:
RewriteEngine On
Options FollowSymlinks
RewriteBase /
# redirect abc.com to
www.xyz.com/abc/
RewriteCond %{HTTP_HOST} abc.com [NC]
RewriteCond %{REQUEST_URI} !abc/ [NC]
RewriteRule ^(.*)$ abc/$1 [L]
NOTES:
[NC] means no case sensitivity
[L] means the last rule in the set
B. For each subweb, modify the .htaccess file in the following directories:
Subweb itself
_vti_bin directory within the subweb
_vti_adm directory within the _vti_bin directory
_vti_aut directory within the _vti_bin directory
The modification to make is to change
Options None
To
Options +FollowSymlinks
***
If there is no "Options" line in the .htaccess files mentioned in step B, then add the line after the ignore line (which is usually towards the very top).
