If the FrontPage Server Extensions are not available on the target Webserver, you can still use FrontPage to develop your Web pages. For example,you can develop the Web by using the Microsoft Personal Web Server on yourcomputer and then transferring your Web content to the target Web server.Keep in mind that when you do this, you may lose some features orexperience some incompatibilities between your working server and thetarget server. This article discusses features to avoid if you arepublishing your content to a server on which you have not installed theFrontPage Server Extensions and how to handle these incompatibilities.
If your Web server and operating system are compatible with the FrontPageServer Extensions, ask your service provider to install them. If theFrontPage Server Extensions do not currently support your Web server andoperating system, you can submit a suggestion asking Microsoft to provideextensions for your server. Microsoft welcomes suggestions or commentsabout changes in functionality and product design. NOTE: To determine whether your server and operating system are compatibleWith the FrontPage Server Extensions, please see the following MicrosoftWorld Wide Web site:
Avoiding Browse-Time WebBot Components
Most WebBot components affect the Web only at authoring time. Forexample, a WebBot Include component or WebBot Table of Contents componentaffects the page it is on only when that page or some other page iscreated or modified. These WebBot components are inactive at browse-time.However, some WebBot components, especially those that are usedwith forms, rely on the FrontPage Server Extensions at browse-time.If you are transferring your files to a Web server on which theFrontPage Server Extensions are not installed, you should avoidusing the following WebBot components:
WebBot Confirmation Field component WebBot Discussion component WebBot Guest Book component WebBot Registration component WebBot Save Results component WebBot Scheduled Image component WebBot Scheduled Include component WebBot Search component
If you use any of these WebBot components, customers who browse your WebSite may receive an "HTTP 404" error when using the corresponding form.
Avoiding FrontPage Image Maps in FrontPage 1.0
Image maps created with FrontPage 1.0 rely on the FrontPage ServerExtensions at browse-time. To avoid problems at browse-time, you shoulduse The image map utility that is supported by your Web server.
FrontPage 1.1 is capable of generating both client-side image maps andnative image maps for several server types. For more information aboutthis feature, click Web Settings on the Tools menu in FrontPage Explorer,and then click the Advanced tab. When a browser is capable of using aclient-side image map, it will use this instead of a server-side image map.
Avoiding Server Incompatibilities
If possible, develop your content on the same type of Web server that youare using for your target Web server. If this is not possible, avoidincompatibilities between your working server and your target server.Some potential trouble areas include the following:
Access control does not carry over between Web servers of differenttypes. You will have to re-enter any access control information for thenew server.
File Name Extensions:
Different Web servers may have different rules for mapping filename extensions to Multipurpose Internet Mail Extensions (MIME) types.For example, a Windows-based server may recognize only .htm as HyperTextMarkup Language (HTML), while a UNIX-based server may recognize only .html.
NOTE: You can reconfigure your working server to match the target server.The FrontPage wizards and templates generate pages that have the .htmextension. If possible, you should make sure that your target serverrecognizes the .htm extension for HTML files.
Different Web servers have different conventions for naming the defaultpage. For example, the CERN server recognizes Welcome.html (amongothers) by default, while NCSA 1.4 recognizes Index.html. Note that youcan reconfigure your working server to match the target server. FrontPagewill create the home page document with whatever name the workingserver provides.For additional information about configuring the default homepage for the FrontPage Personal Web Server, click the article number below to view the article in the Microsoft Knowledge Base:
FP: How to Use a Document Other Than Index.htm as Default Page
Transferring the Content
Once your content has been developed and tested on your working server,you can copy or transfer the files via File Transfer Protocol (FTP) to thetarget server. The following files and folders should not be transferred:
All folders beginning with _vti_:
These folders contain information for use only when the FrontPageServer Extensions are present.
Access Control Files:
These files vary depending on the type of Web server. In general, youshould remove all files that begin with a period if you are transferringfiles to a UNIX server, and you should remove all files that begin withthe number sign (#) if you are moving files to a Windows-based server.
NOTE: If you are using FrontPage 1.1, you can obtain the Microsoft WebPublishing Wizard to automate the FTP process. It will warn you if yourWeb contains files that will not work on a server that does not have theFrontPage Server Extensions. And, it will copy only the files that do workto the destination server. You can download the Web Publishing Wizard fromthe following Microsoft World Wide Web site:
For additional information about publishing your web to a server that does nothave the FrontPage Server Extensions installed, click the article number below to view the article in the Microsoft Knowledge Base:
FP: How to Publish Your Web to a Server w/o FrontPage Extensions
front page explorer editor personal Web server vermeer extensions bot bots publish mspws fppws