| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Hello, I grepped through the various news groups for NOF 9 and have seen the problem descriptions and advice from the gracious folks who monitor this space. However, I've followed all of the advice provided, including the web site at http://www.1ahost.co.uk/html/net_objects.html and saving a GLOBAL profile and either I'm not following the directions fully or there are bugs in NOF9 or a lack of explanation which is still preventing me from being able to set up a Local or a Remote version of my site. I have 2 issues which are no doubt related: 1) When I attempt to publish whether locally or remotely using ANY of the profiles I have the checkbox for the Versions Manager is grayed out. 2) When I click on the Versions Manager from the File Menu whether in Page view or other views, I always get the error message "A connection to the Versions Manager could not be established..............." Here are the actions I have taken. 1) I logged on via an external FTP Client to my web server and created the directory called VersionBackups (full path is /VersionBackups) 2) In NOF 9 from Publish Settings I created a new Publishing Profile and I also called it VersionBackups. I saved this as a Global Profile and NOF 9 duplicated this profile automatically. Now I have the one I just created, and a duplicate profile with the name Global VersionBackups. I pointed both to my web server and to the /VersionBackups directory. Suspiciously the Global VersionBackups Profile does NOT appear within the Versioning tab on Tools -> Options -> Current Site GUI. 3) From Tools -> Options -> Current Site then Versioning Tab I set the newly created profile name for the Versions Manager and used the /VersionBackups as the path. I filled in the rest of the Versions Manager settings as well and clicked OK. 4) It does not appear to me that the Versions Manager settings I just made are saved however. I go directly back into Tools -> Options -> Current Site and then the Versioning tab and the profile for the Versions Manager is set to <none> again. I have tried various methods to see if they might help NOF to remember these settings, but to no avail. Thank you in advance to the NOF community for answering these posts. Brian Erle |
|
#2
| |||
| |||
| Brian, Have you read the articles in the npower group? It has been discussed there as well. - Here is JJ's snippet from that group that has always worked for me and my non techie clients. The only difference is that there is update three now..., but I will assume you have them already. - Just worked straight out of the box. You don't create the folders. NOF does it all for you. I assume you are using the absolute latest version of NOF9 http://netobjects.com/update/install...F9_Update2.exe and nPower http://netobjects.com/update/install...ER_Update2.exe ? Note the following way of setting up which is a little strange, but do the following: Create the NOF9 file/web pages as per normal, then ensure you have filled out the "Versioning" information under Current Site Options (found under "Tools" "Options" "Current site" in top menu - then "Versioning" tab) This is where you create a normal publish profile to your web server and the Repository path for instance "/repository" (without the " "). Then you click PUBLISH SITE icon at top as if you were just Publishing normally . This will create a Rollback point, the /repository directory etc. automatically. You then go into nPower and "Open from a Remote Template" and it will open that file from your web server. You need to "Save As" to the hard disk as well at this point as you do in NOF9. You can then publish from nPower as you do in NOF9 once you've made changes. The standard publishing information and repository path needs to either be typed in or you can in fact create an .nfc file out of NOF9 with this information already created if you want to give this to a customer. When you publish or exit the program it will ask you for publishing/versioning information. Now, the slightly tricky bit that caught me out first time: If you want to make changes along with your client at this point, you DON'T open your original NOF file, you go into NOF9 and select "File" "Open from Remote Template" type in your Web Server information credentials again and select Save As and save it as something like "Original File Name-nPower" (this is what I do). Now it all works like clockwork. You can go back and forth with changes, rollback using "File" "Versioning Manager" etc. It's all pretty logical and definitely works using this method. Bert "Brian Erle" <berle@stny.rr.com> wrote in message news:eh0qeu$2dp1@flsun90netnews01.netobjects.com.. . > Hello, > I grepped through the various news groups for NOF 9 and have seen the > problem descriptions and advice from the gracious folks who monitor this > space. However, I've followed all of the advice provided, including the > web site at http://www.1ahost.co.uk/html/net_objects.html and saving a > GLOBAL profile and either I'm not following the directions fully or there > are bugs in NOF9 or a lack of explanation which is still preventing me > from being able to set up a Local or a Remote version of my site. I have 2 > issues which are no doubt related: > > 1) When I attempt to publish whether locally or remotely using ANY of the > profiles I have the checkbox for the Versions Manager is grayed out. > > 2) When I click on the Versions Manager from the File Menu whether in > Page view or other views, I always get the error message "A connection to > the Versions Manager could not be established..............." > > Here are the actions I have taken. > > 1) I logged on via an external FTP Client to my web server and created > the directory called VersionBackups (full path is /VersionBackups) > > 2) In NOF 9 from Publish Settings I created a new Publishing Profile and > I also called it VersionBackups. I saved this as a Global Profile and NOF > 9 duplicated this profile automatically. Now I have the one I just > created, and a duplicate profile with the name Global VersionBackups. I > pointed both to my web server and to the /VersionBackups directory. > Suspiciously the Global VersionBackups Profile does NOT appear within the > Versioning tab on Tools -> Options -> Current Site GUI. > > 3) From Tools -> Options -> Current Site then Versioning Tab I set the > newly created profile name for the Versions Manager and used the > /VersionBackups as the path. I filled in the rest of the Versions Manager > settings as well and clicked OK. > > 4) It does not appear to me that the Versions Manager settings I just > made are saved however. I go directly back into Tools -> Options -> > Current Site and then the Versioning tab and the profile for the Versions > Manager is set to <none> again. I have tried various methods to see if > they might help NOF to remember these settings, but to no avail. > > Thank you in advance to the NOF community for answering these posts. > > Brian Erle |
|
#3
| |||
| |||
| Thank You Bert for your reply. I do not have the nPower product however. I do have update 3 I believe as NOF 9 shows it to be 9.1 (9.10.0000.5029). I'll take it up with support as I feel the Versioning information ought to be saved and it is not. Brian TheBox wrote: > Brian, > > Have you read the articles in the npower group? It has been discussed there > as well. > - > Here is JJ's snippet from that group that has always worked for me and my > non techie clients. The only difference is that there is update three > now..., but I will assume you have them already. > - > Just worked straight out of the box. You don't create the folders. NOF > does it all for you. > > I assume you are using the absolute latest version of NOF9 > http://netobjects.com/update/install...F9_Update2.exe and nPower > http://netobjects.com/update/install...ER_Update2.exe ? > > Note the following way of setting up which is a little strange, but do the > following: > > Create the NOF9 file/web pages as per normal, then ensure you have filled > out the "Versioning" information under Current Site Options (found under > "Tools" "Options" "Current site" in top menu - then "Versioning" tab) > > This is where you create a normal publish profile to your web server and the > Repository path for instance "/repository" (without the " "). > > Then you click PUBLISH SITE icon at top as if you were just Publishing > normally . This will create a Rollback point, the /repository directory > etc. automatically. > > You then go into nPower and "Open from a Remote Template" and it will open > that file from your web server. You need to "Save As" to the hard disk as > well at this point as you do in NOF9. > > You can then publish from nPower as you do in NOF9 once you've made changes. > The standard publishing information and repository path needs to either be > typed in or you can in fact create an .nfc file out of NOF9 with this > information already created if you want to give this to a customer. > > When you publish or exit the program it will ask you for > publishing/versioning information. > > Now, the slightly tricky bit that caught me out first time: > > If you want to make changes along with your client at this point, you DON'T > open your original NOF file, you go into NOF9 and select "File" "Open from > Remote Template" type in your Web Server information credentials again and > select Save As and save it as something like "Original File Name-nPower" > (this is what I do). > > Now it all works like clockwork. > > You can go back and forth with changes, rollback using "File" "Versioning > Manager" etc. > > It's all pretty logical and definitely works using this method. > > Bert > > "Brian Erle" <berle@stny.rr.com> wrote in message > news:eh0qeu$2dp1@flsun90netnews01.netobjects.com.. . >> Hello, >> I grepped through the various news groups for NOF 9 and have seen the >> problem descriptions and advice from the gracious folks who monitor this >> space. However, I've followed all of the advice provided, including the >> web site at http://www.1ahost.co.uk/html/net_objects.html and saving a >> GLOBAL profile and either I'm not following the directions fully or there >> are bugs in NOF9 or a lack of explanation which is still preventing me >> from being able to set up a Local or a Remote version of my site. I have 2 >> issues which are no doubt related: >> >> 1) When I attempt to publish whether locally or remotely using ANY of the >> profiles I have the checkbox for the Versions Manager is grayed out. >> >> 2) When I click on the Versions Manager from the File Menu whether in >> Page view or other views, I always get the error message "A connection to >> the Versions Manager could not be established..............." >> >> Here are the actions I have taken. >> >> 1) I logged on via an external FTP Client to my web server and created >> the directory called VersionBackups (full path is /VersionBackups) >> >> 2) In NOF 9 from Publish Settings I created a new Publishing Profile and >> I also called it VersionBackups. I saved this as a Global Profile and NOF >> 9 duplicated this profile automatically. Now I have the one I just >> created, and a duplicate profile with the name Global VersionBackups. I >> pointed both to my web server and to the /VersionBackups directory. >> Suspiciously the Global VersionBackups Profile does NOT appear within the >> Versioning tab on Tools -> Options -> Current Site GUI. >> >> 3) From Tools -> Options -> Current Site then Versioning Tab I set the >> newly created profile name for the Versions Manager and used the >> /VersionBackups as the path. I filled in the rest of the Versions Manager >> settings as well and clicked OK. >> >> 4) It does not appear to me that the Versions Manager settings I just >> made are saved however. I go directly back into Tools -> Options -> >> Current Site and then the Versioning tab and the profile for the Versions >> Manager is set to <none> again. I have tried various methods to see if >> they might help NOF to remember these settings, but to no avail. >> >> Thank you in advance to the NOF community for answering these posts. >> >> Brian Erle > > |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.