I am having a bit of trouble publishing to my registered domain, where my new VSD site will be replacing an existing Frontpage site. When I asked my provider for connection information, they suggested the following:
Server: ******.easily.co.uk
(this identifies my domain for which I have the necessary username and password)
Remote folder: /web

Using this, the upload from VSD Publish completed OK but, looking on the internet, it was still showing the old website ie no sign of new website which had clearly updated something but I had no idea what.

Speaking to the provider’s support was not very helpful as they pleaded ignorance of VSD publishing procedures, but they did suggest downloading FTP software Filezilla and doing the upload via that. Having downloaded it, I could at least now see where the update had gone wrong – the website data should be held within a folder /web but the VSD publish had created a sub-folder /web within the already existing folder /web and added my website data there. As a result I ended up with URLs of http://www.mywebsite.org.uk/web
(For info, when I tried VSD Publish entering www in remote folder, this produced a URL of http://www.mywebsite.org.uk/www so it is at least consistent)

So I thought I would try Publishing leaving Remote Folder blank so that it would not create a /web subfolder. But this update did not work.

I see how I could upload my website data to the correct place using Filezilla but I would far prefer to use the proper method ie the VSD Publish facility.

Has anyone else experienced a similar problem and can offer any advice?

John

When you were looking at your server with Filezilla, was the old site under /web?
If so then that is where the new one needs to go.
If not, then the new site needs to go where the old is currently.
I would delete the old site from the server before uploading the new one (or rename the directory it is in to "current directory_save" or some such thing).
Then when you upload via VSD you'll have a clearer picture as to just what is going on.

Try making it web/

Hello Rodgw,

The old site is still there and can be seen with Filezilla as sitting under /web (the higher level one, not the sub-folder /web that that my publish created within /web. I have now deleted this sub-folder)

When you say "that is where the new one needs to go" do you mean I should enter /web in the Remote Folder parameter when publishing. But that is exactly what I did and have explained what seems to happen when i do so. In fact, I tried this again after I had deleted the sub-folder /web but the same thing happened again, not too surprisingly I suppose. So i deleted the sub-folder again.

When you suggest deleting the old site, do you mean deleting the contents of /web or do you suggest deleting the folder itself as well as its contents.

Thanks for your suggestions

John

Hello Eric,

I tried out your suggestion but web/ produced the same result as /web ie it created a /web subfolder within the main /web folder and added all my new website data into that subfolder. So, once again, i can see my new website on the internet if i use URL http://www.mywebsite.org.uk/web

John

Instead of /web, try using just a slash (/) for Remote Folder.

Hello Per,

I tried that but got the same update error as when i tried leaving it completely blank. Error screen is attached.

John

I don't know if this is any help, but just in case... with my Yahoo account, I needed to delete all my old site files that had been made with their sitebuilder. I don't know if your host/Frontpage does this, but sitebuilder uploads to an already existing (blank) index page. I learned (the hard way ) not to delete this index page - just delete all the other pages and then delete just the index page files so a blank index page was all that remained on the server. Then when I uploaded my new VSD site, my new VSD index page was able to "claim" that empty index page space, rather than getting sent to a sub-folder.

I had one instance, that when I renamed the "root directory" in this case "/web_save" then uploaded using the /"whatever directory name", VSD created the directory and all worked.
I like paintbrush's idea, never tried that, but should work too.

Hello Paintbrush,

Using Filezilla I tried deleting the /web folder containing the old website data. This seemed to go ahead OK but, when it had finished, most of the folders within /web were still there although all the individual files were deleted with the exception of one, _vti_inf_html, which i believe is a Frontpage thingy to do with Frontpage extensions.

When I subsequently tried to delete an individual folder within /web, the delete seemed to go ahead, there were a few blinks on the screen but the folder was still there when the blinking finished.

Nevertheless, without any real hope of success, I tried publishing again using /web as the remote folder but, surpise surprise, the same thing happened as before.

So i was not able to properly test out your idea of deleting the old data then publishing.

John