Yes, that is VSD. It IS possible to add custom code, but for that you need the programme itself. The site owner or the site builder should buy you a copy. - And the site builder still has to import the latest version of the pages. But let Viv or someone else who uses VSD tell you the details

Thanks folks.

The situation with VSD is getting clearer. I care about my clients and, despite everything else, I ultimately want to fix the problem so all this information is appreciated. Especially interesting is any workaround or method to safely add custom code to VSD because, if I'm going to build it again, I really need to know that they can make edits to their site without my help in the future.

First I guess you are not aware you can download a fully functional trial version of VSD from the CC store

I would suggest you do this first, you can import all the website into your copy of the program from them, or of the server, so you are on the same playing field

In the top left corner of the page you will see edit, and from there add files

Put everything necessary in there, so every time an edit is uploaded it has it on board

There is an html tool also to put your custom code required (way beyond me) but as a professional coder i am sure it will be self explanatory

Then send everything back to your client in a zipped up folder

I would suggest naming it something like feb 2013 professional edit so they know in future which version to use

You might have fun getting them to re open and install it, simple for a techy (not me)

But when they upload it to the server all should be well in the world once more

That no doubt will be about 5 or 6 chargeable hours, but unlike their comparison, here we have laid good foundations for any future re build

Personally though sorry to disagree with everyone else on this, should you not have checked what program it was written in before offering to carry out any work on it, a quick look at the source code would or should have set off alarm bells, especially if you have never used Coffeecup Visual Site designer Build 7 for windows

Someone sends me a load of mixed broken jewellery and asks me to make a signet ring out of it, its no good me moaning afterwards that my casting is all full of porosity and splitting badly, just to discover lots of what they gave me was rolled gold or gold plated steel or aluminium, I have to test it myself first

Viv,

Isn't it so that VSD also uploads a .vnu file (into a Backup folder), and that this file is needed in order to be able to import the site back into VSD on another machine? The pages can't be imported just like that.

Agreed, there really is no "import" in VSD, it's only able to open it's own .vnu files. You need that .vnu file and I believe a folder that holds the files it uses if I recall? Might just be the .vnu file, haven't used it so not sure on that part.

Glange Custom code is inserted using a "HTML Box" In the edit menu you can add to the header and add meta information. It has to be done within VSD and then the files will be correctly updated. All JavaScript code can be inserted this way. Included Iframes

.vnu file is in the back up folder on the server

but if they get the files from the client its probably a safer way

All a bit technical for an amateur like me !

Yes, as I remember from when I was playing a bit with VSD (some 5 years ago), you also need the 'files' folder, and the folder structure has to be the same as on the computer that has the original files. Have them sent over by the site builder, and send them back when you are done.

There used to be a lot of questions in the VSD forum about migrating a VSD-made site from one computer to another, and if two persons are working on the same site on two computers, you really have to keep your wits straight.. I would shy away from it, I'm glad I'm dealing with code.

The sharing of a site is easy if you follow these steps.
1.User#1 Create a new site with out adding anything to the pages and save it to a dedicated folder named vsdshare.
2. User#1 Now browse to the vsdshare folder and place a folder in side it called something like "content".
3. User#1 Any images or files you want to add to your site you add them to this folder first then when you want to use them in your site you browse to this folder. After adding the files save and publish.
4. User#1 Now with Coffeecups Direct FTP upload the entire vsdshare folder to your server.
5. User #2 Use Direct FTP to down load the whole vsdshare folder to their pc. They can open the vnu file inside with VSD and make changes to the site and hit save and VSD will save the changes made back to the site inside the vsdshare folder. User#2 also adds any files they will use to the "content" folder before adding them to the pages. Save and Publish site.
6. User#2 Now uses Direct FTP to upload the vsdshare folder back to the server.
7. User # 1 can now use direct FTP to download the site back to the same location on their pc if they wish and and begin making changes then repeat the process.

The secret is to save the site to a dedicated folder. I recommend on your desktop. Don't name the dedicated folder the same as any other directory on your server. Keep a "content" folder for all the files you use to create your site inside this folder. Always open the vnu that is in the latest download inside the dedicated folder. Users can't be publishing and working on sites at the same time. It's like playing catch. I have the ball then I'll throw it to you to play with then when your done you throw it back.
Hope this helps anybody wanting to try this.

Sounds like THE way of doing it, Eric. I hope glange gets along with the site and that the hostility of the site builder vanishes. AND that they follow up on this.