NetObjects
Products and Services Partners Support
Company Purchase
Known Issues

subheadline
CRASHERS

1. Crash when Fusion is started
Solution: S1043

When you start Fusion, a "vapor-launch," or system error (e.g., crash, freeze, error type 2). Occasionally, you get the Welcome dialog, can enter in a new site name, click OK – then crash.

If you are using version 8.0 of a localized OS, you will need to upgrade to system 8.1. Most likely, there is an extension conflict - Fusion 3.0 requires the following list of extensions to be turned on:

  • In the Extensions Folder:
    AppleScriptLib, Color Picker, Navigation, Quicktime VRLib, Quicktime(TM), Quicktime(TM) MPEG Extension, Quicktime(TM) Musical Instruments, Quicktime(TM) PowerPlug, Quicktime(TM) VR
  • In the Control Panel folder:
    Quicktime(TM) Settings - version 2.5, 16,145 bytes

2. Crash when Mouse-Over Inserted HTML Icon
Solution: S1435

If you enter more than 255 characters into the Insert HTML dialog box, and then mouse-over the resulting HTML icon, Fusion will unexpectedly crash. You can avoid this by limiting the number of characters you add to the Insert HTML dialog box, or by using the Object HTML feature rather than the Insert HTML feature.

3. Crash When You Undo/Redo Paste of Text Plus Embedded Object
No Solution Object

If you select a block of text which includes an embedded object (e.g., image), copy and paste it into a Fusion page, and then Undo + Redo the operation, Fusion returns a system error (e.g., crash, error Type 2).

4. Crash When You Create Two New Folders in Publish View, Then Undo Twice
No Solution Object

If you add two new folders to Publish view, and then choose Edit > Undo twice in succession, Fusion returns a system error (e.g., crash, error Type 2).

5. Crash When Switching to Assets View in Migrated Fusion 2.0x Site
No Solution Object

If you open a Fusion 2.0x site with an internal data object, switching to Assets view causes Fusion to return a system error (e.g., crash, error Type 3).

Back to Top 

subheadline
MIGRATION

1. Characters Converted in Fusion 2.01 Site Opened in Fusion 3.0
Solution: S1445

If you base a new NetObjects Fusion 3.0 site on a NetObjects Fusion 2.01 site, extended characters (e.g., quotation marks, apostrophes) appear as completely different characters.

2. Dynabuttons No Longer Work in Migrated Fusion 2.0x Web Site
Solution: S1195

Fusion 2.0x does not always register the Dynabuttons.zip file correctly in the Assets list. As a result, Fusion 3.0 does not add Dynabuttons.zip to the Assets list when you migrate the file. When you publish the web site, Dynabuttons.zip is not published, and the Dynabuttons component does not work as expected. To fix, delete and add the Dynabutton component back to the page.

Additionally similar problems can occur with other components such as SiteMapper and Message Board. Follow similar procedures to fix.

3. FormsHandler No Longer Works in Migrated Fusion 2.0x Web Site
Solution: S1268

If you migrate a web site which contains the FormsHandler component, from an earlier version of NetObjects Fusion into NetObjects Fusion 3.0 for the Macintosh, the FormsHandler component may lose the links to its Success and Error pages. To correct this problem, select the Submit button, and recreate the links to the Success and Error pages in Fusion's Properties palette.

4. Dynabutton Labels Don't Update When You Rename Pages
Solution: S1441

The Dynabutton component generates navigation button images when you link the component's buttons. The button images automatically contain the name of the page each button links to. The images are not dynamically updated when you make changes to the linked pages (e.g., change a page's name). Relinking the component's buttons to the desired pages enables the component to generate new navigation button images that contain the updated page names.

Back to Top 

subheadline
ACTIONS

1. Action Targeting Layout Unexpectedly Affects All Elements in Fusion 3.0 Page
Solution: S1290

Although the Object Tree displays the Layout area and MasterBorder area as two different objects, they are not. The two areas are separated in the Object Tree for ease of locating elements in each. Using the Layout area as the target for an action will apply that action to elements in the Layout area, as well as elements in the MasterBorder. When you wish to cascade a single action to a number of elements, place the elements into a Layout Region, and then select the Layout Region as the target of the action.

2. Action's Target Lost When Action Targets Trigger Container
No Solution Object

If the trigger element initiates an action which targets the element containing the action's trigger- the action does not retain the correct target.

3. Fly-In Action nullifies inserted <CENTER> tag
No Solution Object

Place a fly-in action on a gif and it disrupts a center tag placed in beginning of body.

(Create a new blank site -- put center tag in Beginning of Body - Layout Script. Place image on page and then place fly-in on page loaded action on image. Preview the site and the <center> tag is ignored. In Fusion, delete action from image - preview - centers as expected.

Back to Top 

subheadline
COMPONENTS

1. Dynabuttons Do Not Display in IE 3.01 for the Macintosh
Solution: S1328

Internet Explorer 3.0 for the Macintosh does not support many standard implementations of Java applets, and JavaScript. Internet Explorer 3.0 for the Macintosh does, however, support a Microsoft-proprietary implementation of JavaScript, called JScript. If you view a Fusion 2.0x web site which contains Dynabuttons, the Dynabuttons do not appear in the page. If you view a Fusion 3.0 for Windows web site which contains Dynabuttons, the Dynabutton images appear, but do not change when moused-over.

Dynabuttons appear as expected in IE 4.x and NN 3.x and 4.x

2. Dynabuttons Do Not Display Properly When Using a Custom SiteStyle
Solution: S1495

The fontface on the Dynabuttons component does not appear as defined in the current SiteStyle when a new custom SiteStyle or edited existing SiteStyle is used. The fontface appears as a large 14-16pt block text.

3. Dynabuttons Initial Save After Inserting Component Appears to Hang Fusion
No Solution Object

With an existing site or with a new blank site, saving the site after inserting the Dynabutton component on the site can will appear to hang Fusion. On a new site, add the component, configure the Properties palette, and save the site. The initial save can take as long as 2-3 minutes. It will appear as if Fusion has hung and so you may force quit the application. With large existing sites, saving the site after inserting the component can take as long as 10-15 minutes.

4. Picture Rollover Cannot Unlink a Link
No Solution Object

After inserting the Picture Rollover component and assigning a link – the component cannot be unlinked. The link can be changed but not deleted.

5. Sitemapper Component Doesn't Work After Local Publish
No Solution Object

If you add the Sitemapper component to your Fusion site, and publish the site locally, the Sitemapper component will not work. The web browser returns an error message, does nothing, or prompts you to save the file "Sitemapper.html." The component works correctly in sites viewed from a web server.

6. Message Board Component Doesn't Work if Publishing to Macintosh Server (WebSTAR)
No Solution Object

The New Message button does not work. When clicked, a javascript or browser error will result.

7. Forms-Handler Component – Required Fields show up in Properties palette when Publish is set to Email
No Solution Object

Create a form and name the form elements "1", "2", etc so that required fields can be used. Set the Publish To setting to Email and the required field settings will appear in the Properties palette. You can only set required fields if publishing the form to a server (mac, unix, windows). You cannot and should not be able to set required fields for publishing to Email since the cgi script is not used to process the form. A mailto is used when publishing to Email.

8. Forms-Handler Component – Remote URL does not work
Solution Object S1044

When you try to use a remote URL for the form post, the post will fail. The reason the post will fail is because NOF generates the wrong HTML code. Essentially file:/// is generated where http:// should be.

Back to Top 

subheadline
DATAOBJECTS

1. Filters Not Preserved for FileMaker Pro Database.
No Solution Object

If you define a filter for an imported FileMaker Pro database, Fusion discards the filter information if you switch between the datalist page and any other page twice. If you set the filter definitions right before publishing the site, the definitions will stay intact.

2. Type 2 Error occurs with Filter for Internal Data Objects
No Solution Object

Type 2 Error occurs if set the Field popup in the Query dialogue to "Image File," and any text is typed in the search field. Doing a text search on an image is illegal.

Back to Top 

subheadline
IMPORT

1. Contents of Imported HTML Pages Placed Into Multiple Nested Layout Regions
No Solution Object

When you import Fusion-generated HTML into Fusion 3.0, page contents are placed into multiple each page contains multiple nested Layout regions, and page content is nested inside the Layout Regions. You must make your page wider, move your page content into the new white space, and delete the nested Layout Regions to ensure you can edit your pages as expected.

2. JavaScript - Using Functions Called in BODY Tag Don't Work After Importing Site into Fusion 3.0
Solution: S1003

Fusion's Import engine does not support JavaScript functions in the BODY tag of imported documents. Because the Import engine supports JavaScript code in the HEAD section and BODY section of imported documents, replacing the missing function into the BODY tag enables the script to run as expected.

3. Animated GIFs Converted to Auto-generated Single Frame Images When You Import Template into Fusion 3.0
No Solution Object

If you import a template that contains one or more animated GIF images, the animated GIFs may be converted into auto-generated images, and will no longer appear animated when viewed in a browser. You should replace the converted images with the original animated GIFs.

4. HTTP 1.1 or Outdated Browser Message Appears in Page After Remote Import into Fusion
Solution: S1418

Fusion's import engine uses HTTP 1.0 to access and download files from web servers. Fusion's import engine does not support HTTP 1.1. When you import a web site from a server which uses HTTP 1.1, an error message appears, or Fusion creates a single page in Site view.

Fusion's import engine identifies itself to remote web servers as Netscape Navigator 3.0. When you access a site with Navigator 3.0, or another browser which has since been updated by the manufacturer, some web servers display a page prompting you to upgrade your browser. If you try to import a web site from a server which displays an "upgrade your browser" page, Fusion only imports that page.

You must download your web site using a third-party FTP utility, and perform a Local Site Import to bring your web site into Fusion if your service provider uses HTTP 1.1 to transfer files, or if your server displays an "upgrade your browser" page.

To date, the only major service provider that requires HTTP 1.1 compliance is Earthlink Networks.

5. Frameset Pages Blank When You View Imported Site
Solution: S1450

When you import a local or remote web site, Fusion automatically assigns the Import MasterBorder to all imported pages. For each imported page that uses frames, Fusion creates a top level frameset page and one or more child pages for each frame. The frameset page contains the referenced (and therefore not edited by Fusion) HTML of the frameset page, and each child page contains the contents of the frame it represents.

Fusion does not correctly handle referenced HTML pages when the page uses a MasterBorder other than ZeroMargins. Instead of leaving the referenced HTML intact, Fusion replaces it with a Fusion-generated page that contains no content. When you view the imported web site, frameset pages appear empty.

Assigning the ZeroMargins MasterBorder to all frameset pages enables Fusion to leave the referenced HTML intact (preserving the frameset code), and the page will appear as expected in a web browser. Replacing the referenced HTML frameset page and the child frame source pages with a Fusion frameset page enables the page to appear as expected in a web browser.

Back to Top 

subheadline
INSTALLER

1. "Error while verifying your authorization. Specified volume does not exist. Result code: -35" Occurs When You Start Fusion
No Solution Object

When you install Fusion 3.0, the software which verifies our serial numbers requires there be a writeable drive on your default Apple SCSI busses (0 or 1). If you have your drives hooked up to an external bus, or some other sort of unusual SCSI configuration you can get this error. To fix the problem you need to have a writeable drive connected to one of these busses. To check to see what drives you have hooked up to what busses, you can go to your Utilities folder on your hard drive. The system should have installed a utility called Drive Setup. If you double-click on Drive Setup, this utility will scan you machine for all drives and tell you which bus they are on.

2. Error Occurs Installing Fusion 3.0 Upgrade
Solution: S1424

The Fusion 3.0 Upgrade installer requires Fusion 2.01 or Fusion 2.02 to be installed on your machine. The installer correctly perceives Fusion 2.01 on your hard disk, and the upgrade proceeds as expected. The installer also correctly perceives Fusion 2.02 on your hard disk, and the upgrade proceeds as expected. However, the installer does not correctly perceive the presence of Fusion 2.01 patched to Fusion 2.02 on your machine, and returns the error "NetObjects Fusion 2.0.1 or 2.0.2 must be installed on your computer in order to upgrade to 3.0."

If the Fusion 3.0 Upgrade installer locates a version of Fusion which is not Fusion 2.01 or Fusion 2.02 (e.g., the Fusion trial version), the following error occurs: "NetObjects Fusion 2.0.1 or 2.0.2 must be installed on your computer in order to upgrade to 3.0." Removing all installed versions of Fusion and reinstalling Fusion 2.01 from CD-ROM, enables you to install the Fusion 3.0 Upgrade as expected.

Back to Top 

subheadline
LAYOUT

1. Unable to Paste Elements into Layout Region in Fusion 3.0
Solution: S1210

Elements you paste into a Layout Region appear with an exclamation point icon, and they are not placed back into the Layout Region. Because Layout Regions only toggle into Insert Mode when you drag an element into them, Fusion cannot paste elements into Layout Regions. After you paste an element into a Fusion page, you can drag that element into the Layout Region as expected.

2. Layout Width Unnecessarily Changes After Paste
No Solution Object

Copying and pasting any object between pages needlessly increases the width of your Fusion page.

Back to Top 

subheadline
MASTERBORDERS

1. Anchor Pop-up Menu Not Available in Fusion 3.0 After Deleting Anchor From Cloned MasterBorder
Solution: S1415

Fusion assigns unique asset IDs to each element (e.g., link, image, banner) in your web site, enabling you to affect each one individually and ensuring that Fusion can track each asset correctly. However, if you base a new MasterBorder on an existing MasterBorder which contains an anchor, Fusion does not assign a unique ID to the anchor in the new MasterBorder. If you delete the anchor from either MasterBorder, Fusion still maintains the anchor in the other MasterBorder, but removes the asset from the database. When Fusion encounters an asset which does not have a corresponding asset ID (which means that the asset is no longer listed in the NOD file), unexpected behavior results.

Replacing the anchor in another new MasterBorder which is not based on the MasterBorder which contains the original anchor, enables Fusion to track the anchor asset correctly.

2. MasterBorder Guides Disappear After Undoing Change to Page Size
Solution: S1412

Fusion's Undo system records many operations you perform in Fusion, enabling you to Undo them. The Fusion subsystem responsible for handling each operation is responsible for passing the correct information to Fusion's Undo system. When you change the size of a page's Layout area, Fusion's Layout engine (i.e., Page view) is responsible for recording the Undo information.

When you change the size of a page, the Layout engine records Undo information which does not include the MasterBorder guides. When you Undo the change in page size, the MasterBorder guides do not appear. Clicking on the red slider handles in the ruler re-establishes the guides.

Back to Top 

subheadline
PUBLISHING

1. Publish View – cannot rename auto-generated images
No Solution Object

Cannot rename style/autogenerated images. Fusion will let you change the names of the images, but after it completes the publish, you can see that the renamed images have not been published and the original images have been.

2. Special characters in file or path names will cause errors when trying to Preview or Publish
No Solution Object

Using characters other than a through z, 0 through 9, and the underscore key in file and folder names can cause errors during the publishing routine. The option+f character which is commonly used to denote folder names is problematic as well. So a path to an image called image.gif may be:

Hard Drive: Images f: image.gif

When previewing or publishing a site, if Fusion runs into this character in a file or path name, it will either report a TCP/IP error and quit the publish routine or it will report an error of type –2, -10, -11 and then quit.

3. Unable to Terminate File Transfer During Fusion 3.0 Publish
Solution: S1200

If your FTP connection unexpectedly terminates during the file transfer portion of a publish operation, you are unable to cancel the file transfer. You must force quit the application and republish the site after you restore your FTP connection. Fusion will eventually terminate the transfer but can take quite a bit of time to do so (30 min – 1 hour)

4. Forms-Handler Component's CGI Folder Missing From Publish View
No Solution Object

FormHandler component's CGI-BIN folder doesn't show in Publish view until after you publish your web site. This occurs because some components add assets during publish, so Publish view doesn't refresh the component's folder structure until after you publish.

5. Style Elements Appear in Root Level of Published Site
Solution: S1429

Publish view is not coded to manage SiteStyle background images or DataList icons. As a result, information about these file assets is not available to the Publish engine-- until it generates your site's pages. When the Publish engine encounters a link to a SiteStyle element which is not displayed in Publish view, it detects the error and transfers the element into the default file location (i.e., the root level of your web site).

Back to Top 

subheadline
REFERENCED HTML

1. HEAD Section Information Missing From Referenced HTML Page
No Solution Object

Fusion does not correctly add HEAD section information from Referenced HTML pages to the Fusion page that contains the referenced information. This occurs even after you enable the Append to Current <HEAD> option in the Reference HTML Page dialog box.

Back to Top 

subheadline
STYLES

1. Unexpected Options Appear When Editing Fusion Style
Solution: S1301

Active areas for each style element, introduced in Fusion 3.0, enable you to double-click any style element and replace it with another element, or edit its properties. When the elements of a style extend below the current application window, and a scroll bar appears, Fusion does not track the active areas correctly. If you double-click the active area for the SiteStyle line, Fusion presents you with options to replace the current Data List icon, or customize the style's background. Replacing tall images with smaller images (e.g., BuiltByNOF.gif) until no scroll bar appears in the right side of the window, restores Fusion's ability to track the active area.

Back to Top 

subheadline
TEXT AND IMAGES

1. Unable to Access Dictionary Pop-Up Menu
No Solution Object

If you use the Check Spelling feature in a Fusion NOD file, and then open a second NOD file during the same Fusion session, Fusion disables the Dictionary Language pop-up menu. Quitting and restarting Fusion re-enables the pop-up menu.

2. Text in Successive Paragraphs Doesn't Follow Text Style Settings
No Solution Object

The Following Paragraph option in the Edit Text Styles feature does not function. When applying text styles, you should follow the model of selecting text you want to format, and then applying the desired formatting to that text.

Back to Top 

 

 

Documentation 

 

NetObjects Fusion MX 

 

NetObjects Fusion 5.0 

 

NetObjects Fusion 4.0 

 

NetObjects Fusion 3.0 

 

 

 

NetObjects Fusion 2.0 

 

NetObjects Scriptbuilder 3.0 

 

NetObjects Scriptbuilder 2.0 

 

Search
 

 

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