[l008com]

Has anyone else had this problem? You do a save for web. Then you view your updated web page. And alas, the save for web didn't actually save the file, and your web page hasn't been updated? I've had this a ton lately. On 10.6 and 10.7. With CS5. I don't know if it started when CS5 came out, or after, maybe with an update. But it's been happening very regularly to me.

I'll do a save for web. I'll be saving over another file, because you update much more often than you create. I hit save. It asks me if I want to replace the file, as it already exists. I choose replace. Then it appears to save. No errors, warnings, or anything. It just works. But it doesn't. The file that you saved is nowhere to be found. The old one you were replacing, is still there. Sometimes I have to save to my desktop and manually drag the file into the proper folder in the Finder, because photoshop just won't overwrite the old file. Even when I tell it to.

[Big Mac]

That's odd and very troubling. No error message at all? The first and only time I ever saw a piece of software consistently fail to properly save an update to a file was way back with old donated 286s running DOS in elementary school. I remember that we'd try to save the changes to a text file and the file would only partially save. The first save of the file would always work, but subsequent saves to an existing file would not.

I guess the answer is not to attempt to Save As and then overwrite the previous version of the file. Assuming you actually bought a full priced license to CS5 I'd complain bitterly to Adobe customer service about it.

[Thorzdad]

Are you trying to save the file directly to an active web server?
I've never had a problem with Save for Web correctly over-writing an existing image. But, my workflow is to save the files locally, then transfer everything over to the server.

[l008com]

Yes. My server is a Mac and I connect to it directly via native Apple filesharing. I've been working this way for a good 6 years now. But this phantom save for web issue is very new.

[Thorzdad]

Does the existing file on the server get over-written correctly if you do a simple "Save As..."?

[l008com]

I don't know. I've never tried that as you wouldn't normally save a PSD to a web server. Also, this issue isn't a 100%-of-the-time issue, more like... maybe 50% of the time? I've been doing a lot more coding work than graphics work lately, but, from what I remember, sometimes it works, sometimes it doesn't. And when it doesn't, sometimes you have to repeat again, or repeat again several times, and then it will 'take'. Oh and now that I think of it, I'm pretty sure that one other way I get around the bug, is saving it to the proper folder on my web server but with a wrong name. Then deleting the old file and renaming the new, in the Finder. So it really seems to be a problem with the replacing of the file. But there really shouldn't be any problem. It specifically asks me if I want to replace, and I say yes like I have for years. I suspect this is just some weird bug in Photoshop. Don't worry, $1000 later, and Photoshop CS6 will fix this bug. That will be the only difference between CS5 and CS6. Not just in photoshop, but of the entire suite.

[Thorzdad]

When you do a "Save as..." you can pick a file format. It doesn't have to be PSD.

[l008com]

true, but your results will still be much different than what you get with save for web.

[Thorzdad]

Yes, I realize that. I'm just trying to ascertain whether the problem is strictly with Save For Web, or if Photoshop itself is having an overall issue with saving/overwriting files to the server. I would never suggest using a simple "Save As..." for saving web graphics.

[andi*pandi]

I have had problems before saving to remote servers (or even certain folders on a network). I'd say try Thorzdad's suggestion just to see if it's a location vs app problem.

[Thorzdad]

I've been using Adobe apps for decades, and the general rule-of-thumb has always been to work/save locally, then transfer the files to whatever server/drive you want them on. Directly saving a file across a network from an Adobe app was deeply frowned-upon.