Are there any limitations when publishing with FrontPage?

There are some issues which potential FrontPage users should consider:

1. Web size — This seems to be most critical when a “searchable event” is present in the web (Search, Discussion Forum and Table of Contents). The lengthy process of updating the indices for these functions can lead to the connection timing-out (HTTP 500 Error or “Server “” has timed-out”).

2. Disk Usage — You may create and publish as many child webs as your disk storage space allows. However, for each child web you publish, FrontPage duplicates certain information into indices and hidden files. This adds “overhead”, increasing the storage space required for your files. Microsoft’s documentation notes, “FrontPage 97’s optional full-text search indexes can take up to the same amount of disk space as your textual content.”


There are several precautions which need to be taken to protect the FrontPage extensions on your site if it is housed on the UNIX servers:

a) Do NOT use the Edit Access or File Manager features found in your Webii Control Panel to set passwords, limit access, set file permissions or delete directories or files in a FrontPage web. This should only be done through the options in FrontPage Explorer.

b) Do NOT use regular FTP (such as WS_FTP) to upload files to the server when FrontPage extensions are installed. This may corrupt the extensions, disabling the interactive features available with FrontPage.

NOTE: The exception to this is when loading custom scripts to the cgi-local directory on your site. Instructions for uploading custom CGI scripts is included in the notice you will receive when the extensions are installed.