www.net-numbers.com for FREE Internet Telephone Calls

1AHost Directories Net Objects Fusion Help List All Directories List This Directory

 

Fusion 9 Version Manager

We have been successful in getting the Version Manager to work.

First make sure you have installed the latest update for NOF9 which is available here as is the one for nPower

http://www.netobjects.com/support/html/produpdates.html

Like most people we got the message
A connection to the version manager could not be established. A connection to the version manager must be established to check for the latest version of this site and to access other important features.

So - as Hercule Poirot would say - we got the little grey cells working and decided that, for VM, and nPower to work the files it needed would have to live in a central location. We came to the conclusion that it must live on your web space at your ISP. This meant that the first thing we needed to do was set up the FTP link within NOF and test it using the test connection button to get things going. I don’t think it says that in the book.

Something else you have to remember is that - when you are using the Versioning Manager - NOF is connecting to your site, via FTP, to recover all the versioning information it needs. The effect of this is that there can be a bit of “dwell time” whilst NOF makes the connection and gets the information. So if you fire up NOF and load your site, it will take a few moments whilst it sorts itself out. Bear that in mind. It can seem like NOF has hung for a moment.

The steps we took are listed below

Set up the FTP connection within NOF and test it

1. Set up your parameters within VM manager, number of backups etc. You also need to set up the repository path. This will look something like /your_ISP_root_directory/name_of_your_choice
2. upload the site using NOF FTP ensuring that the “check in current document to the versioning system” check box is checked.
3. check the the VM control panel <file - versions manager> that the version is on your system. Ours was. At this point we got a bit sneaky because we put the actual site name (nod file name) in the description field This will become apparent later.
4. Make some changes to the web site and republish.
5. Check VM again - We had two versions there.

We then went to another system at a different location and set up as follows.

1. Create new blank site and set up FTP as in 1 above
2. Set parameters for VM - same as 2 above
3. open VM through <file - versions manager> and we saw both versions of the site.
4. We did a “save site as” giving the new site the same name as the latest version in the VM description field.
5. There’s probably a better way of doing the next bit because we hadn’t spotted the load from a remote template option at this time but, all we did was perform a rollback and the site was there just as it had been on the other system.

Something else we discovered was that, if you have the site running on two separate systems and fire up a version that is older than the one on the web site then, providing you have the NOF FTP connection set up, NOF will tell you there is a newer version of the site available and ask do you want to update the current nod your working on.

17 November 2005