Files trashed

[2labjohn]

I am useing DW CS6, I recently made a minor change to my general template (copywrite date) and when I saved the file I got the update asscoisted files request which I answered OK to and it updated all of the associated files. Fantastic! When I opened one of the associated files all of the template formating, buttons, images, etc. had been trashed like there are improper links to the source material. I checked the paths, availabilty of material and location, etc., and they all look good. Now most of the associated files got trashed and some did not. What is going on and how do I fix without having to redo each page over again?

I checked history panel to see if I could walk back the changes but there is nothing in the history panel. There is also nothing in Perferences about setting history states. Why no history?

Any help is appreciated.

Thank you

John Munro

[email address removed by Mod. Please be reminded that this is an open forum where email addresses will be harvested]

[Jon Fritz · Accepted solution]

Sounds like a code error was introduced in the last template update that's blanking the page.

Run your template page through the validator at http://validator.w3.org/nu and clean up any structural defects you find. If that doesn't bring it back, we're going to need more info (like the code of your template and a child page) to see if one of the contributors here has an other idea.

[2labjohn]

Thank you Jon,

I ran one of my good files from the server through the Validator and several minor errors were found. I then went to the template and fixed the errors and saved and updated one of the trashed files and everything is back to normal. I then updated all of the remaining files and all looks well. What I don't understand is why some files were trashed and others were not? Oh well, I guess that is just the name of the game. Anyway, thanks for your help and I learned a nice lesson with this problem.

John Munro

http://twolabphotography.com

[pziecina]

You could download the files from your server, as those should still contain the 'unaffected' code.