NetObjects
Products and Services Partners Support
Company Purchase
Known Issues

subheadline
SITE VIEW

Custom Names

Problem: Large Pagenames and/or button names can result in instability

If the page name or button name for a page is excessively long, this can result in file instability.

Solution: Do not create page names or button names which are in excess of 100 characters in length.

Back to Top 

subheadline
PAGE VIEW

Components

Problem: Rotating Picture Component Can Lose Images Because of Import

If a rotating picture component is contained in a nod file, and a template also containing a rotating picture is imported into this nod file, if the page containing the imported component is deleted, the image path information will be lost in the remaining rotating picture component.

Solution: The image information must be replaced in the component properties. No information is lost if the imported component is deleted prior to deleting the page containing the imported component.
 

Problem: Sitemapper Component can get error in script_layout.txt on publish

If a site or template file containing a Sitemapper component is transferred to a different system than the one it was created on, and this system has a different installation directory for NetObjects Fusion, the site will get an error in script_layout.txt when publishing.

Solution: Change the name of the current installation directory so that it is the same as that on the original machine. If that is not possible due to something like a different drive letter do the following: Begin a new blank site and add the Sitemapper component to the home page. Open the site with the error and delete all instances of the Sitemapper component in the file. Return to the new site. Choose Import Section from the File menu when in Site View. Choose the Other Radio button and hit Browse. Select File Type of *.nod. Choose the site file containing the error and click OK. This imports the old site into the new site. Delete the Sitemapper from the home page and place it on the page or pages where it should appear in the site. There will now be two home pages. Copy the content from the old home page to the new home page. Move the children of the old home page in the Site View so that they are children of the new home page. When the old home page no longer has any children, you may delete it from the Site View. NOTE: This is a variation on the procedure outlined in recover.txt.
 

Problem: Autoform Component can get error in forms_handler.cgi on publish

If a site or template file containing an Autoform component is transferred to a different system than the one it was created on, and this system has a different installation directory for NetObjects Fusion, the site will get an error in forms_handler.cgi when publishing.

Solution: Change the name of the current installation directory so that it is the same as that on the original machine. If that is not possible due to something like a different drive letter do the following: Begin a new blank site and add the Autoform component to the home page. Open the site with the error and delete all instances of the Autoform component in the file. Return to the new site. Choose Import Section from the File menu when in Site View. Choose the Other Radio button and hit Browse. Select File Type of *.nod. Choose the site file containing the error and click OK. This imports the old site into the new site. Delete the Autoform from the home page and place it on the page or pages where it should appear in the site. There will now be two home pages. Copy the content from the old home page to the new home page. Move the children of the old home page in the Site View so that they are children of the new home page. When the old home page no longer has any children, you may delete it from the Site View. NOTE: This is a variation on the procedure outlined in recover.txt.
 

DataObjects

Problem: Cannot change field type when using an external data object

If you select a simple text field in an external data object and attempt to change the field type to image, a dialog tells you "You cannot have two fields with the same name."

Solution: Change the name of the field in the field editing dialog. Now change the field type. NetObjects Fusion still considers this as the same field even though you have changed the name. Your simple text field is now of type image.
 

Problem: Accessing Excel 7 files results in the error "External Table isn't in the Expected Format"

If you attempt to connect to an Excel 7 spreadsheet, NetObjects Fusion returns the error "external table isn't in the expected format."

Solution: Save the file as an Excel 5 (Win95) format. This will allow you to establish connectivity with version 2.02.
 

Import

Problem: Importing non-html or non-rtf files using the Import Page command results in non-html preview

If you chose a file with an extension other than .html, .htm, or .rtf the page into which you have imported that file is generated as a file of the same type when the page is previewed, staged or published. E.g. if you choose a .txt file in the Import Page open file dialog, and then preview that page, the generated file will use .txt extension and will display in the browser as such.

Solution: Change the extension for the page in the Custom Names to .htm or .html. You can also convert all files to .html or .rtf before selecting them in the Import Page dialog.
 

Links

Problem: Anchor links may not be created between pages containing Autoframes.

If any page containing an anchor also contains an autoframe, that anchor may not be linked to from any other page in the site.

Solution: Use the External Link option to link to any anchor contained within a framed page. See the Autoframes Usage Note.

Back to Top 

subheadline
STYLE VIEW

Import

Problem: A custom style created in 2.01 for Macintosh does not import into 2.02 for Windows.

If a custom style created in NetObjects Fusion 2.01 for Macintosh is imported into NetObjects Fusion 2.02 for Windows using the Import Style command in the File menu, none of the style elements appear in the style view.

Solution: The style must be recreated in 2.02 for Windows.
 

Back to Top 

subheadline
APPLICATION

Backup

Problem: Automatic backup files from 2.01 for Macintosh cannot be imported into 2.02 for Windows directly.

The naming convention for the 2.01 for Macintosh backup files contains a slash character in the filename. This is an unacceptable naming convention on the Windows platform and the files cannot be copied.

Solution: Rename the backup files before transferring them to a Windows machine.
 

Problem: Crash when backup directory has been set to an unavailable network drive.

If you have set the backup directory to a network drive, and that network drive is not available at the time the file is closed or opened, NetObjects Fusion can crash.

Solution: Always check to ensure that the network connection is available, or always set the backup directory to a local drive.
 

Launch

Problem: The user must choose to make a copy of any 2.0 or 2.01 file opened in 2.02.

When you open a 2.0 or 2.01 file in 2.02 a dialog prompts you to choose to make a copy of your original file to work from as once a file is opened in 2.02 it is not backward compatible with 2.0 or 2.01. If you choose the ‘Cancel' option at this dialog, NetObjects Fusion goes to a blank gray screen. The Open File menu option does not allow another file to be opened.

Solution: Choose one of the files from the recent file list to open a file and try again; or choose the New File option and start a new site. Then choose the Open Site option in the File Menu again. This time choose ‘Yes' to make a copy of the file.
 

Back to Top 

 

 

Search
 

 

© 2001 NetObjects, Inc. All rights reserved. Privacy Policy