If you are using FrontPage you should not use FTP to transfer files as it will corrupt the FrontPage Extensions, disabling certain Web site features and requiring a reinstallation of the Extensions and your site's files.
If you want to incorporate a "searchable event" in your site, and your site contains a large number of files, the process of updating indices for the search function can result in the server timing-out. If your site contains a very large number of files, you may also experience server time-outs when attempting to upload your site or recalculate links.
You can help to eliminate this problem by breaking your "web" into smaller, more manageable webs. This solution, however, means that if you want to work on files in different webs, you must first close the current web and then open the one that contains the file you want to edit.
You can create and publish as many different "child webs" as your disk storage space can accommodate. However, for each child web you publish, FrontPage duplicates certain information into indices and hidden files. This "overhead" increases the storage space required for your files.
If FrontPage Server Extensions are installed on your Web server, you should not use FTP to transfer your Web site files as this may corrupt the extensions, disabling interactive features that rely upon them and requiring a re-install of your site and all of its files.
One exception to this rule is when uploading CGI scripts. In order to upload your scripts, you must use FTP, as FrontPage's Publish function does not transfer files in true ASCII mode. However, you can only FTP safely into the /cgi-bin directory. For more information on using scripts, see Working with Scripts.
|
|
If you are using FrontPage you should not use FTP to transfer files as it will corrupt the FrontPage Extensions, disabling certain Web site features and requiring a reinstallation of the Extensions and your site's files. |
