When you say upload image. I am thinking you have a web site. Don't forget that your browser has a cache.

Adobe will tell you to save your files locally then use the OS facilities to copy them to the server.

Seems pretty bogus to me, though, that Photoshop would imply that the file was saved when it really wasn't.  Writing files from computer applications isn't exactly new technology.  Is this a typical thing with Apple systems?

-Noel

Rik Ramsay wrote:

 

With the latter, PS will go through the whole process and 'look' like it's doing what it's supposed to but the file doesn't change, and you get no errors. It just comes down to Adobe/Apple apps thinking the file is "in use".

How is it possible in 2012 for an application - let alone an insanely expensive professional application - to fail to write a file yet emit no error message?

-Noel

So you're saying you can write an entire file, delete the original file, and rename the freshly written temporary file, all without the slightest indication of a failure?  Even if one were to accept that (which I don't, really, but I don't know OSX very well), knowing that file writing may be problematic you don't already have double- and triple-checks after it's done in place to see that it's been written successfully?

Given my software engineering experience I can well imagine what your management thinks of projects that don't lead to gee-whiz new features they can publish in the features list.  I can also envision what the code looks like (and I'm sure I've seen and cleaned-up worse).  It's clear it's touchy given the trouble you had making it work in the background.  But you folks really need to find the time to make it even more robust.

Please don't get irritated with me for pointing out the obvious.  Channel the energy instead into making your product better.

-Noel

Chris,

I wanted to add some further information about my own experience with this which might help you. I use all of the Creative Suite applications on a daily basis and I work 100% off the office server. It seems this overwrite problem is confined to Photoshop and happens EVERY time I try to overwrite a file when the Finder window has it highlighted. I can save a PDF from InDesign when the PDF is selected and it works no problem. Same with HTML files through Dreamweaver.

Another issue with our setup that is probably not tied to Photoshop but yet only happens with Photoshop is if another member of my team creates a file, .psd for instance, closes it on his computer, I open it, save and then get a warning "can't save this file" (or something to that effect) - the file then disappears from the server. We have been caught out numerous times with this and now leave the file open until we can guarantee it saves.

As I mention, I doubt PS has anything to do with our last issue but it ONLY happens in PS so thought I would point it out. I run CS5.5 on OSX Lion (10.7).

Rik

I just came across this thread from a google search.

I have started to have this exact same issue recently.  I think it may have started with the 10.8 server upgrade.  I am seeing the issue from both a MacPro running 10.7 and a MacBook Air running 10.8.  Both are runing CS5/PS 12.0.4.  That has't changed in a while (both of these systems were working as normal with the same file server previously).  What has changed is the server was recently upgraded to 10.8 (and now 10.8.1)--not sure if this is the issue because I can't pinpoint this issue starting exactly when this update occured.

The difficult thing about this problem is that it doesn't manifest on directories that were created prior to this issue starting for me.  When I create a new directory, then I start having this issue (where I can't overwrite an existing file).  This is a MAJOR PAIN IN THE BUTT because the once-awesome ability to click on the file you want to replace and have its name picked up in the Save for Web dialog and THEN OVERWRITE THE FILE is gone.  What's worse, there is no fail notice, so you think it is working as before, but after checking mod date on the file it is clear it is not updating/overwriting.

I've done a check of file permisssions and even attempted to get permissions identical for all files in two dirs, one which allows overwrite and one which doesn't, to no avail.

I was having a sorta similar issue with Coda 2 saving/overwriting files to newer directories...also seems to have cropped up in same timeframe.

I will check the sys logs on my various systems and see if anything is getting logged...would love to get this issue fixed, its a major time waster to have to delete the file before writing a new one with same name.

UPDATE: nothing found in the logs, but I wasn't able to turn on AFP access logging on the server by following apple's instructions.  After some further testing, I am seeing the modification date of the directory where the target overwrite file is gets updated, but the file is not written.