[QUOTE=Rhythmdvl]
I was under the impression that when you’re in remote view, you see the file structure on the site but not additional files stored in the same directory locally. When you double click a file to open it, Dreamweaver opens the local copy to work on. I only see an updated/revised remote copy if I ‘get’ it first, overwrite my local copy, then open it. It could be my own settings, just something from MX 2004, or I may be off my rocker.
[/QUOTE]
I’m using Dreamweaver 8, and I don’t know if your version handles this differently or not, but mine doesn’t do it quite that way.
In version 8, if you’re in Remote view you see all of, and only, folders and files that have been uploaded to the server. As you said, if there are extra files in your local folder not on the server you don’t see those.
If I open a file in Remote view, that file is first downloaded to my local copy (overwriting it if it exists locally) and then opened. (And you know, now that I think of it I’m surprised that it doesn’t prompt me to confirm the overwrite before it does it. Maybe I turned that off somewhere in the last couple of years and don’t remember it.) So in my version, if you were using Remote View and opened the file, you would see any changes made to the file after it was uploaded.
Obviously, getting the file first would also let you look at the actual version on the server as well.
One other thing to think about is HTML that is created dynamically, using something like PHP or ASP code, particularly if it pulls stored HTML out of a database. It’s conceivable that someone managed to slip some HTML code into your database through a form, and it only shows up at execution time. Looking at the code in Dreamweaver obviously would not show that code saved in a file that was retrieved at execution time.
In this case, pointing your browser at the actual website, displaying the page and doing a view source would show all the code actually sent to the client, whether it was static code or dynamically created. Then you could check your code and see which database file it’s coming from and eliminate it.