P: Saving copy not saving over jpg file

*KenelmHeath857 the latest release, 22.4.2, has an option in preferences under 'File Handling' to check 'Enable legacy "Save As"' and fixes this oh so annoying 'feature'. The only issue now is 22.4.2 is so buggy for me, I'm actually considering rolling back to the previous version. Not just me with issues, my colleague has the same bugs and has already rolled back. And so, on it goes!

Same problem as everyone else and it's really messing up my organization as I like to save any edits over an existing file with the same name. Now I have to look for copy along with the original file name. What is going on? I finally decided to look this up because I knew this wasn't right. https://kirkscustomcabinetsinpomona.com/

Maybe it was just an old habit. And it's been so long I could have already forgotten what it was unless I bust out the old dusty laptop. It's not that big a deal to do that. heh

Seems "Save as a Copy" should solve your concern if it doesn't require any additional steps. IMO, "Save As" now works how it should (prior to the bug). Perhaps just a matter of a tiny learning curve to break the old habit?

yes you can save over an open file. just tried it but you do get this message 

There was never a way to replace the file that I was currently working on, and open. It is the way it was. I'm not talking about saving a copy.

I noticed cause I just replace it now and I have never been able to do so. In the thousands of images that I've retouched.

I don't recall this ever being an issue for me in previous Photoshop versions, or a fail-safe required for this, but what you are trying to do is exactly what "Save a Copy" is for. This is the same functionality found in Illustrator, etc. I think the bases are covered.

Speaking of accidentally overwriting files in Photoshop. I notice that the Legacy Save As option does not have a fail-safe to stop you from overwriting a file that is open.

The way Save As used to work was that if you have a file open, you could not overwrite it if it was open. And you would get a pop up saying "I cannot do that, Dave". (movie ref) Well, now you can overwrite an open file as it is still open.

This can be a problem for those of us used to working with the old Save As function, because if you are working on a layered TIFF file and you are told to save as a flattened Tiff with the same name, while keeping a layered PSD, well THAT accident can happen because you can think, oh I'm working on a layered PSD already, and then close. And then you're left with a flattened TIFF and no layered file. More human error on my part, but it was the way Save As worked and I'm used to it, go figure.

Can we have that fail-safe back? Or option to toggle that on or not? (in case there are others who don't care for it) For sure, this will be a problem down the line with all the layered TIFF files I receive.

@11097072_6321432 "Most users do not know the difference between a 5-minute fix and a five-programmer year fix.  Dealing with the vagaries of an operating system can drive you nuts as a programmer."

This is all definitely true.

I'm no pro-programmer, but I have been coding for over 25 years to one degree or another.  But honestly, I think in this case Adobe has chosen this to be of very low, minimal-effort, priority.  Or a simple small nuisance to users.   In my case it's not.  I save my files (png, jpg) into Unity 3D, which then picks up the file changes and implements those changes within the gaming engine.  That doesn't work if the filename changes and "Copy" is added.  It would save (with "Copy") in Photoshop, then I had to go into Unity, wait for the new file import, apply the image settings manually (Unity bakes an image copy, with metadata connecting them, in a different format), and remap any/all materials using that image to point to the new file.  A 2-10+minute process.  It was literally costing me an hour a day, sometimes more.  So I switched to Windows.  No problem there.  It's not a feature everyone, it's a bug 🙂

The thing is that "Save a Copy" already existed as a separate option in the "Save As" window. So we have had that option if one were concerned about the accidental overwrite problem, it is just that they glitched regular "Save As" and the universe almost imploded. (hyperbole)