Each Web server has a name and a set of properties that define the connection settings NetObjects Fusion 12 uses to publish your site to that location and server. You can select a server or set its properties any time before you publish. The publish profile is stored in the Sitename.nod file.
NetObjects Fusion 12 includes one default server profile, Local Publish, which is your local hard disk in the \Documents and Settings\User\My Documents\NetObjects Fusion 12.0\User Sites\Sitename\Local Publish directory. See Setting Up to Publish Locally to modify the settings for publishing to your local hard disk.
You can modify the default profile, create your own, or delete unneeded profiles. You can also create a global copy of a profile, which makes the profile available across different sites.
The information needed to connect to a remote server is specific to your server. Contact your ISP, hosting company, or Web server administrator for the precise information to enter in these fields. For guidance on the questions you need to ask, see Publish Profile Checklist.
To define a remote server profile:
In Publish view, click Settings on the views bar.
The Publish Settings dialog appears. It is the same dialog you used to set up your local publish profile.
Click New.
A new profile will appear in the list box.
Select one of the following server types:
FTP (File Transfer Protocol). Protocol that allows users to transfer files from one computer to another over the Internet.
SFTP (Secure File Transfer Protocol). Secure version of the FTP protocol. SFTP uses SSL to encrypt the entire user session, thereby protecting the contents of the files and the user’s login name and password from outside sources.
WebDAV. Set of extensions to the HTTP protocol which allows users to collaboratively edit and manage files on remote web servers.
Although many ISPs and hosting companies use a single server to receive FTP files and provide Web hosting, the service you use may have separate servers for receiving FTP files and Web hosting. Select the FTP server to receive your transferred files. Check with your ISP administrator for the correct server to select to receive your files.
Enter a name that identifies the server in the Profile Name box, or use the default name.
Enter information in each field in the Attributes section.
Server is the name or IP number you use to connect to the remote server. This can be your site’s domain name, the name of an intranet server, or the name of your ISP’s server. Confirm this information with your ISP administrator or server administrator.
Directory is the location on the remote server where your site’s HTML files are stored.
Leave this field blank if your site’s Home page should be stored in the home directory of the user ID or server account that you use to transfer your site to a remote server.
If you want your site’s Home page to be stored in a different directory than the home directory, enter the path to the Home page here, such as /public_html/user.
For more information about the directory setting, see Publish Profile Checklist
User name is the name you use to log on to the remote server so you can transfer files to it.
Password is the password that authorizes you to access the server. To publish to the remote server, you need server permissions for adding files and creating directories. If you do not enter a password in this box, a dialog appears when you publish the site. You enter the password in that dialog. You can also select an option for NetObjects Fusion 12 to remember your password so you don’t have to manually enter it each time you publish files.
Live URL is the URL on which the home page will be published. If you fill in the Live URL field with your home page URL, then when you have completed publishing remotely and your site is in place, your browser will open so that you can examine the results. If you leave the Live URL field blank, the browser will not open; in this situation, after publishing your site remotely, you will need to open the browser yourself and type the URL of your home page.
Create a site map for search engines option offers you the possibility to create a map of your site’s URLs when you publish your site remotely. This option is disabled and it will become available only after you specify your home page URL in the Live URL field. If you enable this option, a site map for search engines will be created on the published site.
Click Advanced to specify publish Settings.
Advanced options are not available for WebDAV profiles.
Select the options for your site.
Home page file name. Index is the default page name recognized by most Web servers. Select Current Page Name to set the Home page to use the same name as in Site view. Select Home or Default to set the page as in Home.html and Default.html.
File extension for HTML pages. Select .htm, .html, or .shtml depending on the page extension your browser recognizes. That extension is applied to all HTML files for each page in your site. Click the up and down arrows to see all the options. To add an extension to the list, click the browse button.
Your service provider or hosting company can tell you which extension to use for the Web server.
Make sure you use a page extension that your browser recognizes or it might not display the page properly. If you used the Custom Name dialog in Site view and a file name extension for an individual page, that customized extension overrides the site default for that page. If pages do not seem to publish with the correct extension, custom names that you applied to the pages may be incorrect. Check the names of the affected pages.
The Aliases and Advanced S/FTP tabs are for advanced setup options. See Advanced Publishing.
To create additional publish profiles, click New and repeat the process.
To edit an existing publish profile, select it from the Profile list, make the changes, and click OK.
To duplicate an existing publish profile, select it from the Profile list, and click Duplicate.
To delete an existing profile, select it from the Profile list, click Remove, and click Yes to confirm deletion.
Click Close.
You’re now ready to publish your site.