NEW ISSUES
This section will be updated regularly with bugs found after the release of NetObjects Fusion MX:
When opening NetObjects Fusion MX, cannot connect to server to download updates— "Unable to complete the download. Try again later," error received.
You have bought and registered the new NetObjects Fusion MX; when opening it, it always asks to connect to the server. It connects, retrieves download information, but then returns an error that it couldn’t connect to the updates server.
The updates server has a limit to the number of concurrent users. Eventually it will connect and download the updates.
A manual updater is available at:
SAUpdate6_0000_1_7all.exe
This updater will work for Windows 2000, NT 4.0, 95, 98, and Windows ME.
NetObjects Fusion 5.x sites that contain CSS definition in site-wide text styles will not migrate to NetObjects Fusion MX.
If the site has a site-wide text style with a background color or image, NetObjects Fusion MX will fail to migrate the site. You will receive an error message, such as, “Styles/wsamzaonredyellownav/style.ssx contains invalid path,” and NetObjects Fusion MX will stop the migration of your site.
Workaround: Open your site in NetObjects Fusion 5.x, and edit your text styles so that CSS is no longer used. In most cases, this means resetting the Text Format Background options to Automatic. Then, export your site as a template. In NetObjects Fusion MX, open a new site from your .nft template file.
APPLICATION
Known Issues:
.nod site file size increases every time you open and close your site.
Solution S2062
Workaround: In Site view, select Re-optimize your .nod site file. Make sure to re-optimize your site at least once a week.
Background image disappears when you preview a page.
Solution S2063
If you open NetObjects Fusion and immediately preview a page of your Web site with Netscape 4.7x, your page will preview correctly. However, in NetObjects Fusion, you will not be able to see your background image until you refresh your screen.
Workaround: Press F5, or select Refresh from the Tools menu, to refresh your screen.
Placement of a colon in the Business Name field of Step 3 in the Site wizard, results in exiting the Site wizard without creating a new site.
Solution S2073
You must enter only alphanumeric characters in the Site wizard. If you use a colon in the Business Name field of Step 3, you will exit out of the Site wizard without creating a new site.
Workaround: Enter only alphanumeric characters in the Site wizard.
Usage Notes:
- NetObjects Fusion is optimized for Web sites containing 500 pages or less. If your site contains more than 500 pages, NetObjects recommends that you divide your site into multiple sites of fewer than 500 pages each. You can then connect your sites with external links or custom navigation bars.
- NetObjects Fusion must be installed on each user’s local hard drive. NetObjects Fusion can not be run in a shared environment such as Windows Terminal Server.
- Make sure 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.
- Do not copy and paste components into your site. This is a known issue and will cause instabilities in your .nod site file.
- Do not run two concurrent sessions of NetObjects Fusion. NetObjects Fusion is not an MDI application. If you do run concurrent sessions of NetObjects Fusion, you run the risk of poor performance resulting in file instability. In particular, do not copy and paste components between two concurrent sessions of NetObjects Fusion.
- NetObjects Fusion creates a temporary file, yoursitename.nod.bak, whenever you open your .nod file. As soon as you close your site and exit NetObjects Fusion, NetObjects Fusion deletes the .nod.bak file. This temporary file is created as a safety measure should you ever need to recover your site due to file instability.
- NetObjects Fusion automatically saves a backup.nod file in your \Backups folder when you close your site. By default, the total number of backups is four. 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 have the correct path.
- You can improve performance time in NetObjects Fusion by deselecting Auto Save in the Program tab of the Options dialog. Auto Save saves your site every time you switch views, so by deactivating this function it will take less time to move between views.
However, do be aware that if you deselect Auto Save, and then select Save from the File menu, NetObjects Fusion will only save your site to a temporary file. NetObjects Fusion will not automatically save your site when you exit; however, you will be prompted to save changes. With the above in mind, NetObjects recommends against disabling the Auto Save option.
- When you close a site, open a different site, or exit NetObjects Fusion, NetObjects Fusion compacts your .nod site file. A progress bar is displayed during compaction. If you do not see this progress dialog immediately, it may be obscured by other windows on your screen.
- A typical compaction takes 30 seconds, but it can take up to two minutes if your site consists of hundreds of pages. If you attempt multitasking during the compaction of your .nod file, you may experience slow performance, which is only temporary and lasts as long as it takes NetObjects Fusion to compact the file.
WARNING: Do not select End Task from your Windows Task Manager or give Windows the command to Shut Down during the compaction process.
- Press F5, or select Refresh from the Tools menu, as necessary to update and refresh your screen.
- If you view the NetObjects Fusion application status in the Windows Task Manager, while you are creating a site file from a large template, the application status will show as “Not Responding.” This is normal for processes that are busy with large tasks. You can verify that NetObjects Fusion is running by its effect on CPU Usage.
CRASHERS
Known Issues:
Using the Import Document feature with any Microsoft Word 97 document will cause NetObjects Fusion to crash.
The problem is caused by the way Microsoft Word 97 opens and anchors the HTML tags. For example, Microsoft Word 97 will generate <b><Font></b></font>, whereas the correct HTML tags are <b><Font></Font></b>.
There are two workarounds to this problem:
- Upgrade to Microsoft Word 2000.
- Or, copy and paste the desired text from Microsoft Word into a text editor such as Microsoft Notepad. Remove any special characters that might appear. Then, copy your text in the text editor and paste the text into NetObjects Fusion.
HTML Source tab in Page view causes the computer to crash when scrolling left and right.
Solution S2088
If an object is placed and has a script added to it in the HTML Source tab and this is repeated multiple times, an eventual computer crash will occur.
When inserting ASP code in front of the HTML tag in the HTML Source tab, NetObjects Fusion crashes when switching to and from the HTML Source tab.
Solution S2098
Workaround: Don’t add script to the objects in HTML Source view. Rather add the script to the object in Page Design view.
NetObjects Fusion fails 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 hardware 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 then function properly.
INSTALLATION
Known Issues:
Install stopped by preexisting setup.* files in the Windows\temp directory.
Solution 1505
In some cases, when a version of NetObjects Fusion has been installed recently and you are trying to install NetObjects Fusion MX, 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.
Usage Notes:
If you installed a trial version of NetObjects Fusion, it is recommended that you uninstall the Trial version before installing NetObjects Fusion. When you install NetObjects Fusion over the trial, the serial number registry may not be properly overwritten.
When you uninstall NetObjects Fusion, there will be a few folders and files remaining on the hard drive. Before deleting these files, make sure to move any sites, templates, or styles that you want to keep. When you try to delete these files, Windows will return a message dialog indicating, “Deleting these files may impact registered programs.” This message dialog is safe to ignore so click OK. With the use of Services view, some files will be added to the NetObjects Fusion folder that were not placed with the InstallShield process.
MIGRATION
Known Issues:
META Generator tag not updated after migration.
When migrating a NetObjects Fusion 4.x or 5.x site file into NetObjects Fusion MX, 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.x or 5.x site file before migrating.
Text styles of sites included in NetObjects Fusion 4.0\Templates will not import properly.
Solution S2064
Workaround: Migrate 4.0 templates to NetObjects Fusion MX.
Global preferences for previous versions are not retained after migration.
Solution S1522
When migrating a site from a previous version into NetObjects Fusion MX, 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 MX, these preferences are set to the default settings in the new registry entries.
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 MX—has assets that 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 MX.
The reason for this is because the internal directory structure has changed between the previous version of NetObjects Fusion and version MX. 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 MX. All the assets show up as expected.
Filenames with characters ASCII >127 are not portable between Mac OS 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 MX for Windows.
Usage Notes:
How to migrate sites from other NetObjects products. View the detailed section below on migrating sites from previous versions of NetObjects products.
ACTIONS
Known Issues:
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.
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 check box 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.
Center tag will not work with Actions or using Fixed Page Layout in Netscape 4.51/4.61/6.0 or Microsoft Internet Explorer 5.x.
Solution S1877
The center tag won’t work if you use an 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.
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.
ASSETS
Usage Notes:
NetObjects Fusion MX 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 has been placed initially.
Background sounds are always shown as “In Use” in Assets view, even if this option is disabled in the Layout Properties. To remove these assets, you must manually delete them from the Assets view.
BROWSER COMPATIBILITY
Known Issues:
Setting actions in NetObjects Fusion do not display properly in Netscape 6.0.
Solution S2100
This happens in all versions of NetObjects Fusion. This is due to the lack of support for the Layer and ILayer tags for the Action set by Netscape 6.0
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 Layout 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.
Avoid using Netscape Navigator 6.0 if you have any Actions in your Web site. The Actions will not work because Netscape Navigator 6.0 doesn’t support the ILayer or Layer tags, which are used in the NetObjects Action set.
Bring Forward/Send Backward output from NetObjects Fusion may not look or function as expected when viewed in Microsoft Internet Explorer 5.0.
If either the installed path of NetObjects Fusion, the path of the .nod file, or the path of an included object contains high ASCII or DBCS characters, you may observe broken objects when viewed with Internet Explorer. In particular, this may occur when the character set for the page is UTF-8, UTF-7, UCS-2, or any of the supported Asian language character sets. To resolve this, either delete I.E. and only use Netscape or reset the pages character set to the default (ISO-8859-1 for European, Shift+JIS for Japanese).
COMPONENTS
Known Issues:
Migration of Cold Fusion sites with missing components causes errors.
Solution S1753
After migrating a Cold Fusion site into NetObjects Fusion MX, generating the CF table.cfm page results in an error in JAVAI.DLL.
Workaround: Make sure that when you migrate your sites, you have all the components in the directory before you create a new site based on the template.
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 10 a.m. is assigned in the parameters list before an image set to display at 8 a.m., the images are displayed in the incorrect order.
DynaButtons do not function correctly when used with Ticker Tape and CSC and Layers 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 CSC and Layers.
- Publish output structure is set to By Asset Type.
Change any one of these circumstances to fix the problem.
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 apples, in order to accept targets, they must have a specific target parameter coded. None of these apples have this parameter available at this time.
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 Mapped and the Ticker Tape components.
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.
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 canceled, the Screen Door is replaced on your page in the location of the mouse-click.
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.
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.
Usage Notes:
DO NOT copy and paste components. This is a known corrupter of your site file.
To view NetObjects Fusion components you must first publish your site, either locally or remotely. If you preview, you see a place holder 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.
When migrating a NetObjects Fusion 5.0 site to NetObjects Fusion MX, you must have the same components installed for both versions. If you have components in your NetObjects Fusion 5.0 site file that are not installed for NetObjects Fusion MX, you will receive a “Damaged objects found and deleted” error when you import the NetObjects Fusion 5.0 site into NetObjects Fusion MX.
livelier components are not supported in NetObjects Fusion MX.
Domino to Fusion Connector ((DFC) versions 1.0 and 1.1 are not compatible with NetObjects Fusion MX.
Warning: If you open a site containing DFC 1.0/1.1 in NetObjects Fusion MX, you will experience a crash.
For NetObjects Fusion MX you will need to download the DFC 2.0 from the following location: ftp://support.netobjects.com/Public/DFC11a.zip and extract them to your NetObjects Fusion MX 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.
DATA OBJECTS
Known Issues:
NetObjects Fusion MX returns “File is not in expected format” error when connecting to Excel 97 Workbook files.
Solution S1282
NetObjects Fusion MX 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.
External data source does not add database file as asset.
Solution S2077
Workaround: To move entire site from one machine to another with the database, use the following steps:
- Export the site as a template.
- Then, copy the template to the media that is being used to transfer the files.
- Copy the database to the media.
- Move the files to the new computer.
- Make an ODBC connection on the new computer with the same name as the old ODBC connection on the old computer.
- Create a new site based on the template.
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.
Excel spreadsheets with a non-unique first column will replicate records the number of times the first column is not unique.
Solution 2086
For example, if the first column is a category with five non-unique rows, all with category set to Arts & Crafts, NetObjects Fusion MX will create five copies of the first row and ignore the other four rows.
Workaround: Add a first column that has a unique number in it. You must first delete the Stacked Pages and the Data List. Then add the new column and recreate the Data List.
Tab-delimited text file cannot be brought into 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.
Layout does not resize to Data List if site set to Fixed Page Layout.
Solution S1937
Users should use Dynamic Page or Regular Tables when working with data lists.
The Data List 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 List and the bottom of the Layout, or set the HTML generation for the Layout to Dynamic Page Layout or Regular Tables.
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 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.
Do not use Master Borders on your Stacked pages. This causes publishing problems.
FORMS
Known Issues:
SiteMiner Service does not work when the Layout of the page is set to a form.
Solution S2082
Workaround: Add the SiteMiner to a different form area.
Usage Notes:
Forms can not exist on a page that the Browser Compatibility is set to Fixed Page Layout.
IMAGES and STYLES
Known Issues:
Copied cropped images do not properly accept the Stretch display option.
Solution S1236
When an image that 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.
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 that use transparency with the anti-aliased text color of choice before publishing your site to the Web.
Usage Notes:
NetObjects Fusion MX 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 MX color picker.
IMPORT
Known Issues:
It is possible to import certain non-HTML documents through the Import HTML Page option in Page view.
Solution S2065
You could receive an error stating the following: error “The page it too large to be loaded. You can reduce the size of the page by using smaller font sizes (the font sizes can be set in Style view), or you can open the page when you run Fusion on Windows NT.”
When you import a Word document, the name of the publish directory will change to the name of the document.
Solution S2066
Upon importing a Word document into a NetObjects Fusion MX site, the publish directory structure and HTML file names are altered to the name of the document that was imported. You will need to rename the page in Publish View.
An error can occur when importing a large External HTML page.
Solution S2080
When a very large External HTML is set to “Convert to NetObjects Fusion,” an error will occur from Site view that the page is too large to be opened.
Workaround: Limit the size of the External HTML page to the file size of about 20-50K.
Importing a NetObjects Fusion 5.x generated site with HTML Output set to Fixed Page Layout does not layout properly in NetObjects Fusion MX.
Solution S2092
When you import a NetObjects Fusion 5.x site with Fixed Page Layout into NetObjects Fusion MX, the objects will be jumbled or scattered on the page. Solution is to rearrange objects on the page.
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 indicating that it cannot connect. You will need to enter in the IP address of the HTTP server instead of its DNS name.
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.
Some scripts do not import, even when they are located in NetObjects Fusion-accessible locations.
Solution S1003, S1544
If you have an HTML page that you are importing, even though scripts may exist in areas that are supported in NetObjects Fusion’s 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.
Image maps are not imported when importing an HTML file.
Solution S1451
If you have an HTML page or site that 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.
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.
Usage Notes:
HTML files that you plan to import should not contain spaces or accented, double-byte, or illegal characters such as “%,” “*,” and “&;. 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 %,*, &, ;, and . in their file names.
Some remote sites use robots (special scripts) to restrict HTML import. NetObjects Fusion MX 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 on to 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 unless you import a Web site created by NetObjects Fusion. 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.
If the imported Web site was created using NetObjects Fusion MX, the frames will be imported as AutoFrames. If the imported site was created using an earlier version of NetObjects Fusion, the frames will be imported forming complete pages, but without using AutoFrames.
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, re-edit 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.
INTERNATIONAL
Usage Notes:
The latest version of IME provided with Internet Explorer 5.5 will not work with NetObjects Fusion MX. You will need to use the IME provided with Internet Explorer 5.0 or a third party.
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 point work correctly, but sizes larger than 12 point 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 pop-up text boxes. This problem only occurs with Windows 95/98. If the Euro symbol is placed in a pop-up 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.
JAVA and ACTIVEX
Known Issues:
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.
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 .ocx files) that are installed on your system. For example, the following ActiveX controls are known to cause problems with NetObjects Fusion:
- 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 Multi-page 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. Insert ActiveX control, close NetObjects Fusion, and reopen site.
If an ActiveX control does not place correctly on a page or causes a crash, launch NetObjects Fusion MX again and an auto recovery will be implemented. To place a control that 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.
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.
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.
PUBLISHING
Known Issues:
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 that contains them has been selected to be published. The components that exhibit this behavior include:
- Ad Banner
- Message Board
- Site Mapper
- DynaButtons
- Rollover Picture
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 sub menu under the Publish menu in Publish View. You must first select the Clear All Customizations option in the same location.
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 full advantage of this 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 ü 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.
SOFTWARE COMPATIBILITY
Known Issues:
Conflict With Norton System Doctor.
Solution S1083
When exporting a NetObjects Fusion MX site as a template while running Norton SystemWorks 3.00 in the background, NetObjects Fusion MX indicates there is not enough disk space. The problem is that Norton System 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 will only occur if you go to Page view before exporting the template. The error will not occur when the System Doctor is not active.
TABLES
Known Issues:
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 copy and pasted or dragged and dropped into a table cell, the linked text is automatically assigned to the Default setting (Times New Roman, 12 point). This only occurs for tables, not for text boxes.
Usage Notes:
The Table tool in NetObjects Fusion supports all HTML table features, including rowspan and colspan, alignment options, embedded objects, and cell formatting. For more information on how to use the table tool, consult the Adding Tables chapter in the NetObjects Fusion MX User Guide PDF.
TEXT and STYLES
Known Issues:
Hover color function will not work on visited links.
Solution S2072
The hover and the visited links are misordered in the generated style.css and site.css files.
Workaround: Open the style.css and the site.css files in Notepad from the Web server and switch the “A:hover” and the “A:visited” lines of code around. Save the file to the server.
This will need to be done every time the site is published.
Text formatting is lost after creating a link to the text.
Solution S2070
Text formatting of any kind is lost after creating a link to the text.
Workaround: If you would like to override the CSS setting for a link, perform the following steps:
- Highlight the link you would like to change.
- Click the Link tab in the Text Properties palette.
- Click the Format button.
- In the Link Settings dialog box, make the changes that you would like for the link.
- Click OK.
UNDO/REDO
Known Issues:
Unable to undo scripts written in master border HTML.
Solution S2067
This happens in Between Head Tags, Inside Body Tag, and Beginning of Body sections of the HTML dialog box.
Undo/Redo does not change the DynaButton properties.
Solution S1054
You must alter any DynaButton properties by selecting the property and changing its value individually.
Undo/Redo does not reverse added images to any components that 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
Undo/Redo of RTF import loses data.
Solution S1256
If an RTF file is copied and pasted into NetObjects Fusion MX, 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
