NetObjects
Products and Services Partners Support
Company Purchase
Known Issues

subheadline
APPLICATION

Usage Notes
NetObjects Fusion 5.0.2 is optimized for Web sites containing 500 pages or less. If your site contains more than 500 pages, NetObjects recommends that you divide it into multiple sites of less than 500 pages each. You can then connect them by using External links.

NetObjects Fusion sites should reside on your local hard drive. Make sure that you have sufficient disk space to store your .nod file and associated files on the same hard disk where NetObjects Fusion is installed. Avoid working from a network drive or a removable drive such as SyQuest and Iomega drives. Some customers choose to mount their removable drives as fixed disks. Although this is less risky, NetObjects strongly recommends against it.

Because NetObjects Fusion 5.0.2 is not an MDI application, you should not run two concurrent sessions. If you do, you run the risk of poor performance and possible file instability. In particular, avoid copying and pasting components between two concurrent sessions of NetObjects Fusion 5.0.2.

NetObjects Fusion creates a temporary file called sitename.nod.bak while your .nod file is open and being edited. As soon as you exit and your site is completely closed, this .bak file is deleted. The automatic backup feature places backup .nod files in a folder called \Backups. If you ever need to use a backup .nod file, be sure to drag it from \Backups into your \User Sites\Sitename folder before opening it so all the assets will be pathed correctly.

NetObjects Fusion automatically saves a backup copy of your site when the file is closed. By default the total number of backups kept is set to two. NetObjects recommends that you increase this number for added protection against crashes or unforeseen problems with the file or system. A good number of backups is five, though the total number you keep should be consistent with the amount of disk space available.

You can improve performance in NetObjects Fusion 5.0.2 by choosing to deactivate the Auto save option in the Tools | Options dialog. The Auto save function saves your site automatically every time you switch views. By deactivating this function, you can improve performance time when moving through the product. If you do choose to deactivate this function, be aware that NetObjects Fusion only saves information to the temp file when you select Save from the File menu. NetObjects Fusion does not automatically save your site when you exit, but instead prompts you to save changes.

The default method of closing a NetObjects Fusion site involves compacting the .nod file. This occurs when you exit NetObjects Fusion or open a different site. When compaction starts, NetObjects Fusion 5.0.2 lets you know that it is still working by displaying a progress dialog box. If you do not see this progress dialog box immediately, it may be obscured by other open windows on your screen. If you attempt to multitask when this dialog box is present, you may experience slow performance. If this sluggishness exists, it is only temporary and lasts as long as it takes NetObjects Fusion to compact. A typical compaction takes 30 seconds, but can take up to two minutes if the site consists of hundreds of pages.

WARNING: It is very important that you neither End Task nor shut down Windows during the compaction process.

If you wish to avoid sluggishness during closing, select Options from the Tools menu, and on the Program tab, clear the Compact database upon exit option. If you do this, note that you will not benefit from database verification during compaction. NetObjects recommends that you do not turn off compaction.

The F5 key causes screen refresh in most areas of the NetObjects Fusion 5.0.2 application. If you notice that certain elements seem not to have updated or refreshed properly, press F5 to refresh the view.

When you create a site file from a large template, the Task Manager status will indicate that the process is not responding. This is normal for processes that are busy with large tasks. You can verify that NetObjects Fusion is actually running since it is using most of the CPU time.

Back to Top 

subheadline
CRASHERS

Known Issues

Failure to launch when using Diamond Monster video cards and drivers.
Solution S1245
NetObjects Fusion crashes or hangs on launch if the system is using a Diamond Monster video card with drivers, and acceleration is turned on, or the display is set to greater than 256 colors.

If you are using the latest drivers, go into the advanced settings for the card and turn off hardware acceleration, NetObjects Fusion will function properly.

Using the Import Document feature with any Word 97 document will cause NetObjects Fusion to crash.
The problem is caused by the way MS Word 97 opens and anchors the HTML tags. For example, MS Word 97 will generate <b><Font></b></font> where it should be <b><Font></Font></b>.

There are two workarounds to this problem:

1) Upgrade to MS Word 2000. Importing a MS Word 2000 document does not cause this problem.

2) Manually copy and paste the desired text from Word into a text editor such as Notepad. Remove any special characters that may appear. Then copy and paste the text from the text editor to NetObjects Fusion.

Back to Top 

subheadline
INSTALLATION

Usage Notes
In some cases, when you have installed a previous version of NetObjects Fusion recently, you will receive an error message during installation, reporting that the installer was unable to overwrite files in the Windows/Temp directory. If this occurs, make sure you clean out the Windows/Temp directory on your machine and then run the installer again.

If you installed a trial version of NetObjects Fusion 5.0.2, it is recommended that you uninstall the Trial version before installing NetObjects Fusion 5.0.2. When you install NetObjects Fusion 5.0.2 over the trial, the serial number registry may not be properly overwritten.

When you uninstall NetObjects Fusion 5.0.2, a few folders and files remain on the hard drive. When you try to delete these files, Windows returns a message dialog indicating that “Deleting these files may impact registered programs.” It is safe to ignore and to click OK to this message dialog. With the use of Online view, some files will be added to the NetObjects Fusion 5.0.2 folder that were not placed with the InstallShield process.

Known Issues

1. Install stopped by pre-existing setup.* files in the Windows/temp directory.
Solution 1505
In some cases where a previous version of NetObjects Fusion 4.0 has been installed recently, an error message is shown on install saying that the installer was unable to overwrite files in the Windows/temp directory. If this occurs, make sure to clean out the Windows/temp directory on your machine and then run the installer again.

2. Runtime error and files fail to register during install on Win95a machine.

Install NetObjects Fusion 5.x on a clean Windows 95a machine. Near the end of installation, you will receive a message dialog:
“Runtime error 217 at 0000ECC5.” After clicking OK to this dialog, you will get another dialog saying, “File(s) failed to self-register: C:\NetObjects Fusion 5.x\CoFTP.dll; C:\NetObjects Fusion 5.x\NDom.dll; C:\NetObjects Fusion 5.x\NSX.dll; C:\NetObjects Fusion 5.x\SBEditor.ocx.”

There is an application called “regsvr32.exe” which should exist in the Windows\System directory. This application registers the application specific DLLs. This is an OS specific file that is needed on the machine.

Back to Top 

subheadline
MIGRATION

Known Issues

1. Migrated sites preserve the <META NAME=”Generator" CONTENT=”NetObjects Fusion 4.0.1 for Windows"> tag.
When migrating a NetObjects Fusion 4.0 site file into NetObjects Fusion 5.0.2, the META Generator tag will not be updated. You will need to manually update the tag or remove the META Generator tag from the NetObjects Fusion 4.0 site file before migrating.

2. Tables in sites created in previous versions change formatting after migration.
Solutions S1521, S1538
When migrating a site from a previous version into NetObjects Fusion 5.x, tables contained within that site may grow slightly in size, and cell alignments may be altered. Additionally, tables migrated from version 3.0 sites have the row height checkbox checked, fixing the height of the rows in the table. This is due to more precise implementation of table code in the new table tool.

The new tool provides more diverse formatting, as well as fixes for inaccuracies which existed in previous version´s abilities to properly calculate table sizes in the page layout. If your site contains tables make sure to look over the pages containing tables to verify that the layout and properties are correct.

3. Global preferences for previous versions are not retained after migration.
Solution S1522
When migrating a site from a previous version into NetObjects Fusion 5.x, global preferences are not kept. This is because certain preferences are recorded in the specific registry settings for the program. When you install NetObjects Fusion 5.x, these preferences are set to the default settings in the new registry entries.

4. Assets referenced from within a previous version's NetObjects Fusion directory are not retained after migration.
Solutions S1523, S1524
If a site created in a previous version of NetObjects Fusion—other than version 5.0.2—has assets which are referenced to any of the subfolders of the original installation directory, these assets show up as missing when the file is opened in NetObjects Fusion 5.0.2.

The reason for this is because the internal directory structure has changed between the previous version of NetObjects Fusion and version 5.0.2. To avoid this problem, export your site as a template in the original version. Then open a new site based on this template in that version. Once the new site has been saved, open the new site in NetObjects Fusion 5.0.2. All the assets show up as expected.

If you are migrating your site from NetObjects Fusion 5.0, all assets should appear correctly after opening the site file in NetObjects Fusion 5.0.2.

5. Filenames with characters ASCII >127 are not portable between MacOS and Windows.
Solution S1916
NetObjects Fusion 3.0 for Mac sites that use filenames with special characters above ASCII 127 will not properly migrate to NetObjects Fusion 5.0.2 for Windows.

Back to Top 

subheadline
ACTIONS

Usage Notes
Do not use numbers or special characters in custom action messages. Using special characters in custom action messages will cause JavaScript errors. Special characters are non-alphanumeric characters, such as !@#$%^&*()+=[}[]|\"':;<>,/ ?` and ~.

The location of the Actions button for Text Links has been changed. To assign an action to a text link, you will first need to link the text using the Link button. Once you have linked the text, click inside the link. Then go the Link tab of the Text Properties palette and click on the Actions button.

Most browsers do not support placing actions on rollover navigation buttons. Internet Explorer 5.0 is currently the only browser that will support this configuration.

Known Issues

1. Actions on objects embedded in text or table cells cause object misalignment.
Solution S1214
When an action is attached to any element embedded in a text box or table cell, text wrap does not function around that element, and the element is given its own line. At this time, there is no workaround available for this behavior.

2. Netscape crashes on NT when there is a Navigation Bar with Actions and Rollover Buttons.
Solution S1076
If you assign actions to a navigation bar that has the rollover buttons checkbox enabled, when you mouse over the navigation bar using Netscape Navigator 4.x on a Windows NT machine, you can experience a crash. This problem does not occur when viewing page on Windows 95/98.

3. Center tag will not work with a Fly In Action in Netscape 4.51/4.61 or MSIE 5.
Solution S1877
The center tag won´t work if you use a fly in action on your page, even though the page is set to use Dynamic Page Layout. This is because we use DIV and Layers tags when we use Actions. You will need to center the page using Actions. See the Centering a CSS Page note on
NetObjects Workbench.

Back to Top 

subheadline
ASSETS

Usage Notes
NetObjects Fusion 5.0.2 allows you to mark any file asset in your Assets view to be published even when that asset is not In Use. If an asset is marked as “always publish,” it is placed by default in the root of your site's directory structure. You can choose to move the location of this asset to any folder in your output directory structure after it is placed initially. Assets which are marked as “always publish” are NOT marked as In Use, so if you choose to delete all your unused assets, files marked as “always publish” are also deleted.

Background images and background sounds are always shown as In Use in Assets View, even if those options are disabled in the Layout Properties. To remove these assets, you must manually delete them from the Assets View.

Back to Top 

subheadline
BROWSER COMPATIBILITY

Usage Notes
The JavaScript functions document.write() and document.writeln() do not work in Netscape when you select to generate your pages using the Dynamic Page HTML output method. If you are using these scripts, be sure to output your site using the Regular Tables method in Publish view and/or Page view.

Avoid using Netscape Navigator 4.0.15 to preview (or publish locally) sites with actions. A security feature in that version prevents actions from working correctly when you preview or publish locally.

Bring Forward/Send Backward output from NetObjects Fusion may not look or function as expected when viewed in Microsoft Internet Explorer 5.0.

NetObjects Fusion includes files of type *.au and *.wav in the sample files on the installation CD. When you use an .au or .wav file as a background sound on a page, you may see errors in Netscape Navigator 3.01-3.03 when you preview the page. Netscape Navigator 3.04 handles these files correctly. Also, Netscape Navigator 4.0.14 and 4.0.15 will not play *.wav or *.midi as background sounds.

If either the installed path of NetObjects Fusion, the path of the .nod file, or the path of an included object contain high ASCII or DBCS characters, when previewing and viewing with Internet Explorer broken objects may be observed. In particular this may occur when the character set for the page is set to UTF-8, UTF-7, UCS-2 or any of the supported Asian language character sets. To resolve this, either delete IE and only use Netscape OR set the character set for the page to the default character set (ISO-8859-1 for European, SHIFT-JIS for Japanese).

Known Issues

1. Background sound files return errors or do not play in Netscape's browser.
Solution S1535
NetObjects Fusion ships with several files of type *.au and *.wav as part of the sample files included on the disk. When used as background sounds, files of these types can cause errors in Netscape Navigator 3.01-3.03 when pages containing those sounds are previewed. Netscape Navigator 3.04 handles these files correctly. Additionally Netscape Navigator 4.04 and 4.05 do not play *.wav or *.midi as background sounds.

Back to Top 

subheadline
COMPONENTS

Usage Notes
To view NetObjects Fusion components you must first publish your site, either locally or remotely. If you preview, you see a placeholder graphic in the generated HTML page reminding you that you need to publish to view the actual component. This graphic is placed in the same space that the component will occupy on the published page. When publishing locally, some components may not function correctly if they rely on server-side functionality or extensions.

The Components Toolbar always returns to a default position when the product is launched and the toolbar is displayed. This is because NetObjects Fusion component menus are dynamically updated after you install new components on your machine. When the program is started, NetObjects Fusion automatically checks for new components and updates the View | Toolbars > Component Tools menu in Page view with the new component toolbar names.

When migrating a NetObjects Fusion 4.0 site to NetObjects Fusion 5.0.2, you need to have the same components installed for both versions. If you have components in your NetObjects Fusion 4.0 site file that are not installed for NetObjects Fusion 5.0.2, you will receive a "Damage objects found and deleted" error when you import the NetObjects Fusion 4.0 site into NetObjects Fusion 5.0.2.

The Message Board component uses cookies. For the component to function properly, your site visitors must have cookies turned on in their browser settings.

LiveWire components are not supported in NetObjects Fusion 5.0.2.

Domino to NetObjects Fusion Connector (DFC) versions 1.0 and 1.1 are not compatible with NetObjects Fusion 5.0.2. WARNING: If you open a site containing DFC 1.0/1.1 in NetObjects Fusion 5.0.2, you will experience a crash.

For NetObjects Fusion 5.0.2 you will need to download the DFC 1.1a from the followoing location: ftp://support.netobjects.com/Public/DFC11a.zip and extract them to your NetObjects Fusion 5.0.2 Components directory.

Ticker Tape component text will appear partially or not at all after migrating sites from earlier versions. The HTML that is generated by the component is correct. To resolve the problem, copy the file “TickerTape.class” from the Ticker Tape component folder to its corresponding Asset folder and remember to delete the “Local Publish” folder.

Known Issues
1. Correct image is not displayed in Time Based Picture component if times are not assigned in chronological order.
Solution S1203
The times assigned to show images in the Time Based Picture component must be in chronological order. If, for example, an image set to display at 10am is assigned in the parameters list before an image set to display at 8 a.m., the images are displayed in the incorrect order.

2. Message Board component returns a JavaScript error on Reply.
The Message Board returns a JavaScript error when the Reply button is activated only when viewed under Netscape Navigator 3.01. All other versions of Netscape Navigator do not return this error.

3. The Screen Door component does not function correctly on ASP Server.
Solution S1228, S1231
If you have published your site to an ASP server, when viewing the site with IE 3.01 for Macintosh, the redirect takes you to the Netscape 4.0 pages. Additionally ASP code displays for Netscape browsers in right frames when using the Screen Door component with a site which uses frames.

4. DynaButtons do not function correctly when used with Ticker Tape and Fixed Page Layout publishing option.
Solution S1218
DynaButtons do not currently function correctly under the following combination of circumstances:

  • DynaButtons and Ticker Tape are in the same page
  • HTML output is set to Fixed Page Layout
  • Publish output structure is set to By Asset Type

Change any one of these circumstances to fix the problem.

5. Some components do not properly accept frame targets.
Solution S1217
Certain components do not accept frame targets. These components are:

  • Time Based Picture
  • Ticker Tape
  • Ad Banner
  • Go Menu

Because the Time Based Picture, Ticker Tape, and Ad Banner components are Java applets, in order to accept targets, they must have a specific target parameter coded. None of these applets have this parameter available at this time.

6. The Go Menu component does not link correctly when viewed in IE 3.0.
Solution S1536
The Go Menu does not currently function correctly when used in frames and viewed in Internet Explorer 3.0. Only the first selected internal link functions correctly. The next selected link does not function. This is due to JavaScript handling errors in IE 3.0

7. Some components no longer accept accented characters within text display areas.
Solution S1539, S1541
Certain components do not allow accented characters in their text display areas. Any accented characters entered are displayed as the “?” character. This includes the Site Mapper and the Ticker Tape components.

8. The Screen Door component does not function correctly under IE 3.0.
Solution S1543
IE 3.0 does not support JavaScript redirects which are used by the Screen Door component, therefore this component will not function correctly when viewed from IE version 3.0. Later versions of IE 3 (3.01 and 3.02) do support JavaScript redirects.

9. Ad Banner component does not initialize first image in sequence.
Solution S1221
The images assigned to the Ad Banner component may not start with the first assigned image when viewed in a browser. All images remain in the correct sequence, but the start image can vary from session to session.

10. Screen Door dialog and placement incorrect after Undo cut.
Solution S1509
If you place a Screen Door on your page, then select it and cut it, when you choose to undo the cut, an incorrect dialog is called. If this dialog is cancelled, the Screen Door is replaced on your page in the location of the mouse-click.

11. Go Menu and Form Handler components cannot be placed on the same page.
Solution S1622
The Form Handler component does not function correctly if it is in the same form area as the Go Menu component. The submission always fails and the webinfo.txt file is not updated. Make sure that the Go Menu is not in the same form area as the Form Handler. The Go Menu component was not designed to work in a form area.

12. Deleting components does not remove components elements from Publish view.
Solution S1621
When you delete components from a Web site, the component assets are left in use, and the components' folders are retained in the Publish view.

Back to Top 

subheadline
DATA OBJECTS

Usage Notes
If you have two different image fields embedded on a table placed on a stacked page, both of the image fields will display the same image in the generated page.

If you use the “Text files” ISAM driver to bring in a comma-delimited file, you must set the source file to be read-only in order for the operation to succeed.

NetObjects Fusion cannot import tab-delimited files.

Pages containing data objects should be set to have an HTML Output of Dynamic Page Layout or Regular Tables. Fixed Page Layout should not be used on pages containing data objects.

Known Issues

1. NetObjects Fusion 5.0 returns “File is not in Expected format” error when connecting to Excel 97 Workbook files.
Solution S1282
NetObjects Fusion 5.0 does not support ISAM connectivity to Excel Workbook files saved under Excel 97 format. If the file is saved as an Excel 95 file, or the ODBC data source is chosen for the connection protocol, the files can be accessed through the external data object. For more information see our Usage Note.

2. Data fields on stacked pages can publish non-WYSIWYG.
Solution S1215
Data fields on stacked page can publish incorrectly after stacked pages are first created. This will occur if the stacked page is not first viewed in page view before publishing. This can happen to either internal or external data objects. Always make sure to view the stacked page layout before publishing a newly created data list from an existing data object.

3. Tab-delimited text file cannot be brought into NetObjects Fusion.
Solution S1889
When you try to bring in a tab delimited text file as a data object, you will get an error message indicating that the first line of the tab-delimited text file isn't a valid name. You will then get a message saying, “The External Data Object was created correctly, but it contains no data. The Stack Pages will be empty.” After clicking OK to this dialog, NetObjects Fusion brings in an empty data object.

4. Layout does not resize to Data Object if site set to Fixed Page Layout.
Solution S1937
Users should use Dynamic Page or Regular Tables when working with data objects.

The data object spills over the text links and other elements that are in the bottom MasterBorder margin. The Layout has not resized to accommodate the size of the data. Either increase the space between the bottom of the data object and the bottom of the Layout, or set the HTML generation for the Layout to Dynamic Page Layout or Regular Tables.

Back to Top 

subheadline
FORMS

Known Issues

1. Form action not preserved when migrating or inserting NetObjects Fusion 4.0.1 templates.
In NetObjects Fusion 3.x or 4.x site, enter in a form action and export site to a template. Create a new site in NetObjects Fusion 5.0.2 based on that template and the form action will either be converted to a local path or will be deleted. This is a legacy issue with NetObjects Fusion 3.x and 4.x templates. However the problem has been resolved for NetObjects Fusion 5.x templates.

Back to Top 

subheadline
IMAGES AND STYLES

Usage Notes
NetObjects Fusion 5.0.2 anti-aliases fonts in navigation bars, banners, and other auto-generated images by relying on a combination of internal and system resources. The two technologies that our customers can use are Microsoft Font Smoother and Adobe Type Manager (ATM). One of these must be activated on your system to ensure that all font types can be anti-aliased within NetObjects Fusion.

When you use transparent GIFs, be sure that the colors of the foreground image AND the transparent color are both from the 256 Color Browser Safe Web Palette. This palette is included in the NetObjects Fusion 5.0.2 color picker.

When you use transparency colors in style images, it is important to choose colors carefully in order for anti-aliasing of fonts to work correctly. Anti-aliasing works by creating a gradient between two colors, and automatic generation of images uses a fixed color palette. As a result, if colors in an image are too close in value to the transparent color that text is anti-aliased against, portions of the image may be marked as transparent erroneously. Test all images which use transparency with your anti-aliased text color of choice before publishing your site to the Web.

Known Issues
1. Copied cropped images do not properly accept the Stretch display option.
Solution S1236
When an image which has been cropped is copied, applying the stretch display option does not take effect. The image handles must be moved before the Stretch option is properly used when generating the page.

2. Transparency in some style images conflicts with anti-aliased text.
Solution S1537
When using transparency colors in style images or other images, it is important to choose colors carefully if anti-aliasing of fonts is to work correctly. Because anti-aliasing works by creating a gradient between two colors, and because NetObjects Fusion´s automatic generation of images utilizes a fixed color palette, if colors in an image are too close in value to the transparent color which text is anti-aliased against, portions of the image may be assigned as transparent when it is not wanted. Make sure to test all images which use transparency with the anti-aliased text color of choice before publishing your site to the Web.

Back to Top 

subheadline
IMPORT

Usage Notes
HTML files that you plan to import should not contain spaces or accented, double-byte, or illegal characters such as %,*&;. in their file names. Additionally, source files referenced in the HTML code (e.g., pictures or applets) should not contain spaces or illegal characters such as %,*&;. in their file names.

Some remote sites use “robots” (special scripts) to restrict HTML import. NetObjects Fusion 5.0.1 cannot import these sites, and informs you if a site is using robots. Additionally, some remote sites are protected behind firewalls or proxy servers, or do not expose their Web servers to anonymous FTP connections. If any of these situations occur, you must log into your server using your regular FTP client and download the site to a local drive before importing. Then you can import the site by selecting the Local (on this computer or network) option in the Import Web Site dialog.

Importing HTML that contains tags outside the HTML 3.2 specification is not supported (e.g. CSS Text style tags, Layer tags, CSS Positioning tags). If you import HTML with unsupported tags, text and source files will appear in Page view, but the original layout will not be maintained. You can then reposition the text and source files manually.

If you import a Web site that contains frames, NetObjects Fusion will not convert frames into AutoFrames. Instead, NetObjects Fusion will place the content for each frame onto separate pages. The frameset is the parent for these frame pages. This parent is referenced as an external HTML object. The parent and child pages are labeled accordingly in Site view. To reuse this content, you must copy the content from the separate pages and paste it onto one page.

You cannot import Web pages encoded in UTF-7 or UTF-8 while using Windows 95. If you do so, when you view the pages in Page view, you see messages that tell you corrupted text blocks on the page were converted to ASCII. Many of your characters will show up correctly in the text box, but there will be extra garbage characters in the text box as well. This display issue stems from Windows 95 and does not occur if you are using Windows NT. To correct a Windows 95 display, reedit each text box to remove all the garbage characters and then reapply the formatting. If possible, try importing a version of the page that is encoded in a different character set.

Known Issues
1. Unable to import from intranet sites.
Solution S1896
If you try to import an intranet site using the DNS name, i.e. http://XXX/xxx, NetObjects Fusion will return an error indicated that it cannot connect. You will need to enter the IP-address of the http-server instead of it's DNS name.

2. Filenames with spaces are not imported.
Solution S1895
NetObjects Fusion cannot import sites whose filenames contain spaces. Links which contain spaces are treated as external links.

3. Some scripts do not import even when they are located in NetObjects Fusion accessible locations.
Solution S1003, S1544
If you have an HTML page which you are importing, even though scripts may exist in areas which are supported in NetObjects Fusions´ Page HTML dialog, these scripts are not imported. This includes JavaScript events located inside the <BODY> tag, and <CENTER> tags located at the beginning of the body content, before page content begins.

4. Image maps are not imported when importing an HTML file.
Solution S1451
If you have an HTML page or site which you are importing and it contains image maps, these image maps are not imported into NetObjects Fusion. The image to which the map was applied is imported, but any hotspots must be recreated using the Hotspot tool from the Standard Toolbar.

5. Duplicate index files can be created when importing a remote site.
NetObjects Fusion creates a duplicate of the index.html file if the index.html file is not specified in the import dialog. This occurs if the path to the home page is entered in the format: www.sitename.com. To get only one home page use the format: www.sitename.com/index.html.

Back to Top 

subheadline
INTERNATIONAL

Usage Notes
If you set your page character set to UTF-7, and you attempt to change the size of the text in a text box to something greater than 12 point, the size change does not show up in the published HTML. Sizes smaller than 12 work correctly, but sizes larger than 12 do not. To work around this issue, use UTF-8 as your page character set. UTF-8 supports exactly the same set of characters as UTF-7 and does not exhibit the font size problem.

The Euro symbol does not appear properly in popup text boxes. This problem only occurs with Windows 95/98. If the Euro symbol is placed in a popup text box, it will display as a vertical line. This will not affect the display of your page from within NetObjects Fusion or from the generated HTML output.

The Euro symbol will not appear properly in the Site view properties palette if you have set the “Use small fonts in properties palette” option. If you deselect this option, the Euro symbol will appear properly

If you are running Windows 98 Japanese, and you set the page character set to Traditional Chinese (Big5), Simplified Chinese (GB2312) or Korean (KSC5601), you may not be able to type into text blocks. Text that was previously on a page may become invisible when that page is refreshed. To correct this, upgrade to Microsoft Internet Explorer 4.01 SP1, 4.01 SP2, or 5.0. All versions of Internet Explorer are available at http://www.microsoft.com/windows/ie/download/a ll.htm.

If you select Internet Explorer 4.x:

Select the Add-on Windows Internet Features for Internet Explorer 4.0. From the Multi-Language Support section choose the Japanese, Korean, Pan-European, Chinese (Traditional) and Chinese (Simplified) Language Support packages and install. Japanese users should go to http://windowsupdate.microsoft.com  and select “seihin no koushin.” From the resulting list, select the “kankokugo,” “youroppa kakukokugo,” “kantaiji chugokogo,” and “hantaiji chugokugo” Language Support packages and install.

If you select Internet Explorer 5.x:

Select Internet Explorer 5 and Internet tools. Download the ie5setup.exe and run it. In the installer, make sure to add the following Multi-Language Support Packs:

  • Chinese Traditional Text Display (unnecessary if you use a Chinese operating system)
  • Chinese Traditional Text Input (unnecessary if you use a Chinese operating system)
  • Chinese Simplified Text Display (unnecessary if you use a Chinese operating system)
  • Chinese Simplified Text Input (unnecessary if you use a Chinese operating system)
  • Korean Text Display (unnecessary if you use a Korean operating system)
  • Korean Text Input (unnecessary if you use a Korean operating system)
  • Japanese Text Display (unnecessary if you use a Japanese operating system)
  • Japanese Text Input (unnecessary if you use a Japanese operating system)

Back to Top 

subheadline
JAVA AND ACTIVEX

Known Issues

1. ActiveX controls with source files do not function correctly after publishing.
Solution S1013
ActiveX controls that require source files (e.g., Adobe Acrobat PDF, Macromedia Shockwave Flash) do not publish correctly unless you add the source file using Assets view first. Click the Files tab in Assets view and then click the New button. Give the source file a name and then browse for it. Be sure to select “Always publish file.” Then in Publish view, be sure to put the source file in the same folder as the .ocx file. Since this requires a relative assets path, you need to locally or remotely publish to test these types of ActiveX controls.

2. Some ActiveX controls cause errors or can crash NetObjects Fusion.
Solutions S1500, S1517, S1519, S1520, S1297, S1886, S1093
NetObjects Fusion lets customers place ActiveX controls on the page and visually edit their parameters. However NetObjects does not have control over the quality of the various controls (.ocx files) that are installed on your system. For example, the following ActiveX controls are known to cause problems with NetObjects Fusion 5.0:

  • Adobe Acrobat Control for ActiveX will eventually cause NetObjects Fusion to crash with an Invalid Page Fault in module MFC42.DLL. The crash most commonly happens with the 3.0 version of the Adobe Acrobat Control. Upgrading to the 4.0 version of the Adobe Acrobat Control will resolve the crashing.
  • Early versions of Real Media player ActiveX controls return the error “unable to insert the specified control dialog box” and the control is unable to be placed. The Multipage ActiveX control returns error “unable to insert the specified control dialog box” and the control is unable to be placed.
  • RealPlayer ActiveX Control will cause NetObjects Fusion to crash with an Invalid Page Fault in module RMOC3260.DLL and MFC42.DLL if place it and go to Site view and then back to Page view.

If an ActiveX control does not place correctly on a page or causes a crash, revert the site to the last saved backup. To place a control which does not work correctly using the ActiveX tool, use any other method to create the HTML required to place an ActiveX control (such as Microsoft´s ControlPad utility) then place that HTML using the External HTML tool in the page.

3. Java Beans do not function in all versions of Netscape Navigator browsers.
Solution S1518
In order to properly view Java Beans in Netscape browsers, you must have Navigator 4.06 or later. Earlier versions of Navigator will not display the beans.

4. Java Beans return JS errors in IE when the set color action is set to black.
With any action where you can set a color on a bean, if you set that color to black, IE 4.x returns a JS error. All other colors function correctly.

Back to Top 

subheadline
PUBLISHING

Usage Notes:
NetObjects Fusion allows you to publish the entire site, a selected section of the site, or an individual page. However, in order to take advantage of this new feature, the site must be published in its entirety first. If you do not publish the entire site initially, the resulting pages may contain broken links.

You cannot publish external files that have accented characters or double-byte characters in their path name. Once your site is published to a Web server, URLs to Web pages cannot contain these characters, and there is no way of mapping them to something acceptable during publish. Use Windows Explorer to change the file name so that it includes only plain ASCII characters. Then, go back into NetObjects Fusion and link to the external file again with the ASCII-only name.

NetObjects Fusion no longer generates character-entity equivalents for extended ASCII characters (such as &uuml for the u-umlaut character.) These entities are no longer required for modern servers, and are not supported in all international character sets. Because you can now choose the character set for generated HTML in NetObjects Fusion, it is no longer necessary to generate special character-entities.

NetObjects Fusion does not recognize 250 as valid FTP response. When publishing to a server such as an MVS server which gives a 250 reponse to the PUT command, NetObjects Fusion will return an error for each 250 response. NetObjects Fusion currently only accepts the 226 response.

Known Issues

1. Component Assets are uploaded when incremental publish indicates they should not be.
Solution S1534
NetObjects Fusion now has the ability to publish only site sections and individual pages. However, because many components assets are tracked at the site level, these elements are published to the server regardless of whether the page which contains them has been selected to be published. The components which exhibit this behavior include:

  • Ad Banner
  • Message Board
  • Site Mapper
  • DynaButtons
  • Rollover Picture

2. Imported sites initially do not allow selection of Directory Structure to Flat.
Solution S1239
If a site has been imported from HTML, you will need to manually set the Flat directory structure option after the site has been imported. To select a Flat directory structure, choose the By Flat menu option in the Arrange Files submenu under the Publish menu in Publish View. You must first select the “Clear All Customizations” option in the same location.

3. Banner images do not show in Publish view when using a site based on the Blank Site template.
Solution S1513
If you start a site based on the Blank Site template (New Blank Site) the banner image does not automatically show in Publish view so that it´s name and file location may be manipulated. To make the banner image show in Publish view, delete the banner object and replace it using the Banner tool on the Standard Toolbar.

Back to Top 

subheadline
SOFTWARE COMPATIBILITY

Known Issues

1. Conflict With Norton System Doctor.
Solution S1083
When exporting a NetObjects Fusion 5.0.2 site as a template while running Norton SystemWorks 3.00 in the background, NetObjects Fusion 5.0.2 indicates there is not enough disk space. The problem is that Norton Sytem Doctor has locked files that are required to export a template. To resolve this problem, shut down Norton System Doctor.

After installing Norton Utilities 2000, the error will arise when the System Doctor is activated. It would only manifest if one goes to Page view before exporting the template. The error will not occur when the System Doctor is not active.

Back to Top 

subheadline
TABLES

Usage Notes
The table tool in NetObjects Fusion now supports all HTML table features, including rowspan and colspan, alignment options, embedded objects, and cell formatting. For more information on how to use the new table tool, consult the Table Tool chapter in the NetObjects Fusion 5.0.2 User Guide PDF.

Known Issues
1. Linked text in an RTF file imported into a table has font set to Default setting.
Solution S1226
If you have an RTF file containing linked text and all text is formatted to a specific font type and size, when that text is either copied and pasted or dragged and dropped into a table cell the linked text is automatically assigned to the Default setting (Times New Roman, 12 pt.) This only occurs for tables, not for text boxes.

Back to Top 

subheadline
UNDO/REDO

Known Issues

1. Undo/Redo does not change the DynaButton properties.
Solution S1054
You must alter any DynaButton properties by selecting the property and changing it´s value individually.

2. Undo/Redo does not reverse added images to any components which use images.
Solution S1238
The Undo option changes the size of the image only. The affected components include:

  • Ad Banner
  • Rotating Picture
  • Picture Rollover
  • Time Based Picture
  • DynaButtons

3. Undo/Redo of RTF import loses data
Solution S1256
If an RTF file is copied and pasted into NetObjects Fusion 5.0.2, and that copy action is undone, and then redone, some information from the original copy is lost. To re-paste all data, choose the paste option again.

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