|
Does the upgrade require version 2.0x or 3.0x to be installed? The Upgrade version of NetObjects Fusion 4.0 does not require that any previous version be installed on the machine. If you are upgrading from version 2.0x you
are prompted for your 2.0x serial number followed by your new 4.0 serial number. If you are upgrading from version 3.0x, you are prompted for your 3.0x serial number followed by your new 4.0 serial number. If you do
happen to have version 3.0x installed on the same machine onto which you are installing version 4.0, the installer does not prompt you for the 3.0x serial number. Where can I find my 4.0 serial number? The 4.0 serial number is located on the registration card
shipped in the box. All serial numbers for the different bundled products (if serial numbers are required) can be found on two stickers at the bottom of the inside fold of the registration card. Where can I find my 3.0x serial number? Your version 3.0x serial number is available on a
sticker on your half of the registration card which shipped in the box, or it can be found on the splash screen for NetObjects Fusion 3.0x in the Help menu, under About NetObjects Fusion . What do I do if I have lost my serial number? If you do not have a serial number for any product
please contact NetObjects Customer Service:
- US & Canada 1-888-449-6400
- International 1-512-434-1523 For all
- Other questions or inquiries, please email: info@netobjects.com
How can I bring my 2.0x or 3.0x sites into NetObjects Fusion 4.0? If you have
existing site files (*.NOD, *.NFT) that originated in NetObjects Fusion for Windows versions: 2.0, 2.0.1, 2.0.2, 3.0, 3.0.1 or 2.0.2 PE or 2.0.2i (single-byte) international, follow one of the two sets of instructions
below. Also refer to the "If You Are Upgrading..." chapter of the Building Business Web Sites book.1) If you want to migrate a .NOD file, first copy the site's folder into the NetObjects Fusion 4.0\User
Sites folder. Be sure to make a copy, because once you open the site in 4.0, you cannot reopen it in the previous version. After you copy the site's folder, launch NetObjects Fusion 4.0, select Open Site from the File
menu, and open the .NOD file. If you see the Welcome to NetObjects Fusion dialog, choose Open a NetObjects Fusion Site and browse to the .NOD file. When a dialog appears telling you that the file was created in an older
version of NetObjects Fusion, click Yes to open a copy of the file, then give it a new name. When you open, preview, publish, or navigate through the copy of this site, you might see dialogs that warn you about
instability. If this occurs, please consult recover.txt located in the NetObjects Fusion 4.0 directory. If the style elements for the site appear blank, select Add Style to List from the Style menu in Style view, and
open the missing style's .ssf file, located in it's style folder. The style folder might be in the Styles folder of the previous installation directory 2) If you want to migrate a template (.NFT) file, first copy the
template as described in the procedure outlined in section 1) above. Then, in NetObjects Fusion 4.0, you can either import the template as a section of your site or base a new site on the template by opening the
template directly. You might be prompted to open the template file directly before inserting it or basing a new site on it. For more information view the Readme.html file located in your NetObjects Fusion 4.0/Readme
directory. What are some known issues migrating 2.0x or 3.0x site files into 4.0? There are several issues which have come to our attention as things to watch for when you are bringing 2.0x or 3.0x site files forward into version 4.0. The
solution numbers listed below can be found in our on-line knowledgebase at: http://www.netobjects.com/support/html/knowledgebase.html Image fields in
internal dataobjects are lost from sites created in version 2.0x If you base a new site in NetObjects Fusion 4.0 on a template file created in versions 2.0, 2.01 or 2.02, image fields in internal dataobjects do not
properly retain the path to their source files. If possible, open the nod file directly in version 4.0 so as to not lose image paths. Solution S1278Tables in sites created in previous versions change formatting after
migration. When migrating a site from a previous version into NetObjects Fusion 4.0, 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. Solutions S1521, S1538 Global preferences for previous versions are not retained after migration. When migrating a site from a previous version into
NetObjects Fusion 4.0, global preferences are not kept. This is because certain preferences are recorded in the specific registry settings for the program. When you install a new program these preferences are set to the
default settings in the new registry entries. For information on which preferences are global and which are not, please refer to the Preferences chapter in our User Guide PDF file or in our on-line help. Solution S1522
Assets referenced from within a previous version's NetObjects Fusion directory are not retained after migration. If a site created in a previous version of NetObjects Fusion 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 4.0. The reason for this is because the internal directory structure has changed between
the previous version of NetObjects Fusion and version 4.0. 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 4.0. All the assets show up as expected. Solutions S1523, S1524 Stretch properties not retained for images in tables migrated from 2.0x sites. When 2.0x site
files containing images in tables where the image display property is set to the Stretch option, are reported as Normal display in NetObjects Fusion 4.0. In order to fix, select the stretch option, then reselect the
Normal option, or select the Restore Original Size option from the Object menu. Solution S1237 Object HTML Inside Tag content for Text boxes cannot be edited after migration to NetObjects Fusion 4.0. NetObjects Fusion
4.0 no longer has the Inside Tag field option for Text boxes. If any content was placed in this field in previous versions of NetObjects Fusion, this content is no longer editable in version 4.0. Before migration, make
sure to place any scripts or custom code into the Before or After Tag fields for Text boxes. Solution S1608 Instability or erratic behavior. If a site crashes or returns instability errors when opening it in 4.0, this
indicates that the site file contains instabilities which the new 4.0 format is designed to recognize as incorrect behavior. As with previous versions, you can choose to follow the recovery procedure as outlined in the
recover.txt document included in the NetObjects Fusion 4.0 directory, or, to eliminate any possibility of incorrect or incomplete data from an old file being brought forward into a new site, import from already
published HTML using the Import Remote Site Option. |
