Advanced Publishing

From Documentation
Jump to: navigation, search

Advanced Publishing

NetObjects Fusion provides a range of advanced features to deal with a variety of Web publishing requirements. For example, some Web servers require special directory structures to host a website. In addition, some complex sites may need additional publishing settings to make the site function properly.

Customizing Your Site's Directory Structure

Although NetObjects Fusion offers three preconfigured directory structures, you might need to customize your site's directory structure further. Customizing the site's directory structure is usually only necessary if your ISP or host server requires a specific structure for websites. You can customize the site's directory structure in Publish view by renaming, rearranging, or deleting site folders, creating custom folders, or changing the publishing properties for folders, pages, and assets.

A C in the Attributes column of an item in Publish view indicates the item was customized. For example, a directory with a new name or a file moved from one directory to a new directory displays a C in the attributes column.

Customizing your directory structure does not change the appearance, design, or content that your site visitor sees; it only controls how the pages and assets are stored on the server, and the URL to access the site's interior information.

NetObjects Fusion saves the customized directory structure in the Sitename.nod file so you don t have to reconfigure the structure each time you generate the site's HTML files or transfer them to a server.

Creating a Custom Folder

  1. In Publish view, select the folder, page, or asset where you want to add a custom folder, right-click, and select New Folder from the shortcut menu.

NetObjects Fusion adds a custom subfolder named New Folder below the selected folder or file.

  1. Enter a new name for the folder and press Enter or select another object to record the folder name.
  2. Drag other folders or files into the custom folder as needed.

Renaming Folders and Files

  1. In either pane of Publish view, right-click the folder or file and select Rename from the shortcut menu.
  2. Edit the existing object name or enter a new name. Press Enter or select another object to record the new name.

You can rename auto-generated folders and files if they are not locked. NetObjects Fusion auto-generates names of images that you modify in Page view. For example, if you crop an image or set it to be transparent, NetObjects Fusion auto-generates a new name for the altered image. Auto-generated image names are in the format of a_filename.ext where a stands for auto-generated, filename is the name of the original image, and ext is the extension of the image, .gif or .jpg. Auto-generated image names only appear in Publish view.

NetObjects Fusion remembers the new names the next time you generate the HTML files for your site. Any folder or file that you rename is considered customized. If you name a customized folder with a name used by an auto-generated folder, it is still treated as a customized folder.

Aliased folders are also considered customized folders. Publish view displays them in the directory structure, even if they are empty, and tracks their name and location in the event you change them. See Creating Aliased Folders and Setting the CGI-Bin Directory.

By definition you cannot change read-only assets, such as script files and directory files used by NetObjects Fusion Components. NetObjects Fusion ignores attempts to move or rename read-only files. An R attribute and lock symbol in the directory structure indicate a read-only file.

Deleting Folders

  1. In either pane of Publish view, click the folder you want to delete and make sure it is empty. You cannot delete a folder until it is empty, and you cannot delete pages or assets in Publish view.
  2. Right-click the folder and select Delete Folder from the shortcut menu.
  3. NetObjects Fusion deletes the folder.

Rearranging the Directory Structure

In either pane of Publish view, click the folder, page, or asset you want to move and drag it to its new location.

NetObjects Fusion moves the object and updates all references and links to it.

If you move pages, NetObjects Fusion remembers their new locations, but might continue to auto-generate folders needed to contain that page's assets. Components and their related assets have a black lock image on their icons, signifying that they cannot be renamed or rearranged.

Viewing and Setting Publishing Properties

In addition to their other properties, your site's folders, pages, and assets have publishing properties that indicate or control the way they are included in your published site.

Three of these publishing properties indicate the publishing status for that folder, page, or asset:

  • Folders, pages, and assets that were renamed or moved from their default location have a customized publication property. Customized assets display a C in the Attributes column in Publish view, and a checkmark in the Customized option in the Attributes section of the Properties dialog. To see the Properties dialog for a customized asset, select the asset in either pane of Publish view and from the Publish menu, choose Properties.
  • Some folders, pages, and assets are marked read-only:
  • Assets created by NetObjects Fusion components, such as Site Mapper.
  • Dependent Java .class files that were added to the site's assets. When you add a Java object and preview or publish your site, NetObjects Fusion analyzes the object's .class file to see if it calls for other .class files; if so, those dependent .class files are added as read-only assets.

Read-only assets display an R in the Attributes column in Publish view, and a check in the Read-only option of the Properties dialog.

  • Pages and assets have two published date properties that display the latest publication date in both the Last Remote Publish and Last Local Publish columns of Publish view.
  • If an asset was never published locally or remotely, it displays Never Published in red in the appropriate column, and has a check in the Needs Publishing option of the publication Properties dialog. HTML files always appear in red.
  • If an asset was changed since the last time it was transferred to the server, it displays the Last Published date in red, and has a check in the Needs Publishing option of the publication Properties dialog. If you select Publish changed assets only when you publish this site, the assets with red dates are republished to the server. Pages always appear red because they are always republished unless you specifically choose not to publish a page.

To see the publication properties of a folder, page, or asset listed in Publish view:

  1. Right-click the item.
  2. Select Properties from the shortcut menu.

The Properties dialog for the selected item appears.

Suppressing a Page or Asset from the Published Site

You can also suppress publishing for a selected page or asset by setting its Don't Publish property. If you set this property, NetObjects Fusion:

  • Overrides the Needs publishing or Publish changed assets setting for this page or asset.
  • Displays a diagonal red slash mark through the page or file icon in Publish view and adds a D to its Attribute column.
  • Publishes the site without that page or asset.

To suppress publishing for a page or asset:

  1. In Publish view, right-click the page or asset and choose Properties from the shortcut menu.

The Properties dialog appears.

  1. Select Don t publish, then click OK.

NetObjects Fusion displays a red slash through the page or asset icon and suppresses it from the site when published.

To re-enable publishing for a suppressed page or asset, repeat step 1, clear Don't publish, and click OK.

This Don't publish command is not the same as the Don't publish command in Site view. Selecting the Don't publish command in Site view eliminates the pages and all links to it from the published site. In Publish view, the Don't publish command does not eliminate the page from the published site. The page is simply not generated again and not recopied to the site. The page and all links to it remain. The images and assets of the page may be republished, but the page will not.

Creating Aliased Folders and Setting the CGI-Bin Directory

Sometimes you need to store certain assets of your site in a location separate from the rest of your site. For example:

  • You can link to programs such as CGI scripts or other executables that have to be placed in a specific CGI directory so they run properly.
  • You can place an order form or other pages in a secure location that requires authorized access, without restricting access to the rest of your site.
  • You can link to images or other assets that are maintained or controlled by others, and stored in a protected location.

You must create a publish profile with server type as FTP to use an alias. This option is not available for local, SFTP, or WebDAV publish profiles.

To do this, you create alias folders, using a process in which you define two locations: the actual physical location on your Web server where you want to transfer the pages or assets, and the URL or logical address that you want NetObjects Fusion to use when referring to that object. On some servers, this is referred to as creating virtual folders.

After the site is transferred to the Web server, you or your server administrator must configure the server to look in the FTP location for assets that are described as being in the URL location. For example, your site might include several stock images from your company's marketing department, such as the company logo and other approved artwork. When you create your site, you use copies of the artwork that you stored on a local disk. When you transfer your site's HTML files to the company server, however, you want to use the "official" images that have been approved and maintained by the marketing department.

Check with your server administrator to see if your site contents or remote server configuration requires a CGI directory or other aliases.

To specify the CGI-BIN directory:

  1. In Publish view, click the Settings button on the views bar.

The Publish Settings dialog appears.

  1. Choose a profile from the Profile list.
  2. Click Advanced publish settings.

The Advanced Publish Settings dialog appears.

  1. Click the Aliases tab.
  2. Enter the FTP path where CGI scripts are stored in the CGI alias field. This establishes an alias to the executable directory on the server where CGI scripts are kept.

To create other aliased folders:

  1. In Publish view, arrange the directory structure for your site the way you want it to appear on your server.
  2. Isolate the pages or assets you want to store in an aliased location into one branch of the directory structure, under a common parent folder. If necessary, create a custom folder for each set of aliased content.

If your site requires more than one alias'such as one alias for secure pages and another alias for protected assets you can create more than one custom folder.

  1. Drag pages and assets into the appropriate custom folder(s) as needed.
  2. Click Publish Settings on the views bar.

The Publish Settings dialog appears.

  1. Choose a profile from the Select Profile drop-down list.
  2. If necessary, make changes to that profile.
  3. Position the Publish Settings dialog so you have a clear view of the Contents of directory pane in Publish view. Refer to the directory structure to make sure you type the URL to your custom folder correctly.
  4. Click Advanced publish settings and then click the Aliases tab.
  5. To add a new alias, click the New Alias button. To edit an existing alias, select it from the list, then click the Edit Alias button.

The New Alias (or Edit Alias) dialog appears.

  1. Enter the absolute or relative path from your site's root folder to the custom folder containing the aliased pages and assets as the URL Path.

Refer to the directory panel as needed to enter the path exactly as it appears, including the use of uppercase and lowercase names and spaces. For example, if you create a custom folder called Companypix and place it under your Assets folder, the URL Path would be./Companypix.

  1. Enter the FTP path that you want to use to actually store that folder and its contents. This FTP location must be on the same server as the rest of the site because your publish profile only logs onto one server at a time.
  2. Click OK.
  3. To add additional aliases, click New Alias again and repeat the process.

When you publish your site, NetObjects Fusion keeps all links and references to your aliased content pointing toward the URL path, but actually stores the pages and assets in the FTP location you specified.

The server must be configured to support this alias. This is a system administrator task outside of NetObjects Fusion, so you or your server administrator must define the alias on the server.

Setting the Server Port and Permissions

Depending on your Web server configuration, you might need to set specific permissions or a specific port so your Web server software can access your site's HTML files. Setting permissions might override the default permissions normally set by NetObjects Fusion. The permission settings only apply to FTP servers that support the CHMOD command. Windows IIS servers do not support the CHMOD command, therefore to change the permissions on a Windows IIS server, see your server administrator.

To set the server port and permissions:

  1. In Publish view, click the Settings button on the views bar.

The Publish Settings dialog appears.

  1. Choose a profile from the Select Profile drop-down list.
  2. Click Advanced publish settings and then click the Advanced S/FTP tab.
  3. Select options for the Advanced S/FTP settings:
  • Server port is the port from which your server accepts S/FTP connections. By default the port setting is 21, which is the most common ISP setting. However, some security systems or other server configurations may require a different setting. Check with your ISP administrator for the proper server port setting.
  • Default Permissions applies to servers that support the CHMOD FTP command, which covers read, write, and execute permissions. By default, this setting is 0 (zero), which corresponds to no permissions. Check with your ISP administrator or server administrator to see if the server supports the CHMOD command and, if it does, which setting you need. Note that the setting applies to all files and folders uploaded to the server. You cannot set some files or folders to one set of permissions and others to different permissions.
  • Connect passive mode is for publishing to servers not within your company's firewall, or if your ISP or host company's FTP manager establishes connections using passive mode. Passive mode (or PASV) is a security mode in which a client sends a connect signal for data, the server replies with a confirmation signal, and then the data begins uploading. This allows the server to confirm the identity of the client that is connecting before data begins uploading. Although some firewalls allow PASV as a security mode, others may not be configured for PASV. In that case, publishing will not work. Typically, NetObjects Fusion cannot publish through firewalls or proxies. If a message tells you that NetObjects Fusion cannot connect to the server, the problem is usually a firewall preventing you from logging on. Also, in some cases of publishing to a proxy server, the publishing process appears to succeed but the files do not appear on your site.
  1. Click OK.

Publishing with Firewalls or Proxy Servers

If you develop sites behind a firewall and need to publish to a remote server that is outside the firewall, you might be able use FTP passive mode to connect to the server.

  1. In Publish view, click the Settings button on the views bar.
  2. Choose a profile from the Select Profile drop-down list.
  3. Click Advanced publish settings and then click the Advanced FTP tab.
  4. Select Connect passive mode.
  5. Click Close.

If the reverse is true and your remote server is behind a firewall or stored on a proxy server, NetObjects Fusion cannot publish directly to the server. If that's the case, follow these steps:

  1. Publish your site to a local folder other than the \Documents and Settings\User\My Documents\NetObjects Fusion\User Sites\Sitename\Preview folder of your site. Use whatever directory structure and HTML output method you would normally use. The default setting, Local Publish, publishes to the folder \Documents and Settings\User\My Documents\NetObjects Fusion\User Sites\Sitename\Local Publish.
  2. Consult with your server administrator for the preferred method of transferring content to the remote server. Potential methods include:
  • Transferring the entire directory structure of the local site to a holding location on an unprotected server, so an authorized administrator can then transfer the site to the protected location.
  • Using an FTP application such as WS-FTP or other means of access authorized by the server administrator to transfer the entire directory structure of the local site to the protected server.
  • Installing Personal Web Server (PWS) and remotely publishing to it. Then you send the site's files via FTP from PWS to the server.

Whichever method you use, be sure to transfer all files and to duplicate the local folder structure precisely.

Publishing Special Assets

When you transfer your site to the Web server, NetObjects Fusion transfers the entire site to the designated location, including special assets you tell it to manage. These special assets include things like Java classes, images and assets contained on external HTML pages, and CGI scripts. The list of managed assets included in your published site is displayed in Assets view.

When you transfer the site's files to the Web server, you can use any of three methods to ensure that the special assets are included in your site's managed assets.

  • Include the assets when you add the object that refers to them. For example:
  • If you reference external HTML pages using the External HTML tool, NetObjects Fusion analyzes the external pages and, if it finds assets in the external pages, includes those assets in Assets view.
  • If you add Java objects to your pages using the Java tool, NetObjects Fusion analyzes their .class files and adds other .class files referenced there. If you listed additional files on the Java Properties panel, NetObjects Fusion includes them as managed assets. See Inserting a Java Applet or Servlet.
  • You can reference an asset in a file link and NetObjects Fusion manages and publishes the asset. See Creating a File Link.
  • You can explicitly add any special asset to Assets view and select Always publish file to ensure that NetObjects Fusion manages and publishes the asset. If you select Always publish file and do not move the file in Publish view, and then only publish a section of the site, NetObjects Fusion places this asset at the root of the site. See Adding a File Asset.

Managing Script Assets

NetObjects Fusion does not analyze custom scripts that you add to pages, MasterBorders, or other objects. If those scripts reference special assets, they are not automatically included in the site's managed assets. To have NetObjects Fusion manage and publish assets called in custom scripts, you must create file links to those assets, or explicitly add them to Assets view.

When you add the file asset, select Always publish file to ensure that the asset is marked In Use. After publishing the first time, you can clear this setting if you only publish changed assets. Scripts have very specific calls to those files, generally ./imagename.gif, image.gif, or images/imagename.gif for images and cgi-bin/form.cgi, complete http path to form.cgi, or ./form.cgi for .exe files.

  • When you add an asset, and the directory structure is set to by Asset Type, the added asset is always added to the assets\images folder.
  • If you add an asset and the directory structure is set to by Site Section, the added asset is always placed in the root if it is an image, or in the existing cgi-bin if it is an .exe.
  • If the directory structure is set to by Flat, the asset is added to the root.

Be sure to move the added asset to the correct location in Publish view so the file is published to the correct location on the server.