Use this page of the Site Settings dialog box to change how PagePorter converts FrontPage web pages for this project. You can access this dialog box by selecting Site Settings from the PagePorter menu and then choosing the Conversion tab.

Default (Home) Page Name

This section deals with the subject of default pages. The default page is served to the client browser when only a directory name is requested. The most common example is when the browser requests a URL such as http://www.parastream.com. The URL actually requests the root directory of the domain, so the default or “home” page is served. Different web servers, platforms, sites, and even designers often use different names for the default. FrontPage typically uses the filename index.htm for the default page, while ASP.NET typically uses default.aspx. If you ask PagePorter to change the filename of the default page (or any filename in the web for that matter), it will automatically update any links to that page, including any in the navigation structure.

Automatically convert FrontPage default page filenames to the PagePorter default page filename

If this option is checked and FrontPage web pages are selected for conversion, the filename of any FrontPage default pages will be changed to the PagePorter default page filename.

FrontPage default pages

This is a list of filenames that the current web server recognizes as a default page.

Add

Lets you add a filename to the list of FrontPage default pages.

Remove

Lets you remove a filename from the list of FrontPage default pages.

PagePorter default page

Specifies the destination filename to use when converting default pages.

Post-conversion Default Action

After a FrontPage web page is converted to a PagePorter page, you have some choices about what to do with the original FrontPage file.

Remove the FrontPage file from this project

The FrontPage web page is removed from the PagePorter project, and is marked as “don’t publish” for FrontPage. This is the “safest” option in terms of protecting the now obsolete FrontPage page in that it doesn't modify or remove it at all. However, FrontPage will not automatically delete this file from the web the next time you publish from FrontPage. You will have to delete it from the remote web server manually (look for the “don’t publish” status in the list of remote web site files when publishing the site).

Replace the FrontPage page with a link to the PagePorter page

The FrontPage web page content is replaced with a <meta http-equiv="refresh" > tag that causes most browsers to redirect to the new PagePorter web page. For those rare instances where the automatic redirect doesn't work, it also has a regular link. If the FrontPage web page was in the PagePorter project before the conversion, it will be afterward. If you have an investment in having search engines and other sites that link directly to pages in your site, this option keeps the old filename active but replaces the content with a redirect to the new PagePorter page. An excellent choice if you are managing the project from PagePorter only.

Delete the FrontPage page

The FrontPage web page is deleted permanently. This is the cleanest, simplest and most direct way to deal with the situation. An excellent choice for projects managed by both FrontPage and PagePorter, as subsequent publishing from FrontPage will remove the old file from the remote web server. Unfortunately, publishing from Visual Studio .NET using the Copy Project command will not remove deleted project files from the remote web server, and you will have to delete them from the remote web server manually.

Leave the FrontPage file untouched

Do not touch the FrontPage web page at all. Useful when re-converting shared borders after you change them in FrontPage.

Don't convert if errors

Checking this option will pre-scan the FrontPage pages and skip the conversion if there are any errors.