Hej! The old photoshop behaviour used to be that when you save to overwrite an existing file it asks you to confirm that you want to replace it, you say yes, and the old file gets overwritten. In the latest version if you click "replace" it still does not replace the file, but adds "copy of" text at the end after the fact without any way to not do that. Please give us an option to have the old behaviour, or change it back to how it used to be by default.
This issue causes big problems in our design and production workflows when editing images linked to QXP or ID files. The jpg arguments are missing the point. This is happening with all file types where "save as... replace" is selected regardless of layers, flattening, whatever. The dialogue says the file will be overwritten but it is not; instead, a second file is created with "copy" appended to the filename.
Something that maybe help if you need to replace a PNG file, go to File/Export/Quick Export As PNG and the file is replacement without this upset issue, this work for me
Hey Adobe, this has been a known issue for close to 2 years. I'm still on Catalina and a lot of people are saying it's happening on Big Sur. Figure it out. Pause on the cloud library. Put the latest 3D/VR/AR feature to one side. Make this a top priority and then you can continue with a new feature no one wants.
I simply can't understand how a simple bug (because it is obviously a bug, since it contradicts even the option selected by the user to replace the existing file) takes so long and so many versions to be fixed.
I'm not sure here is the correct forum to ask Adobe to fix it.
But dozens of bug reports also didn't work...
For some users, like myself, this is crucial for the workflow. My temporary solution was a script that I run after saving files.
I simply can't understand how a simple bug (because it is obviously a bug, since it contradicts even the option selected by the user to replace the existing file) takes so long and so many versions to be fixed.
I'm not sure here is the correct forum to ask Adobe to fix it.
But dozens of bug reports also didn't work...
For some users, like myself, this is crucial for the workflow. My temporary solution was a script that I run after saving files.
It's not a 'simple' bug at all. It's a complicated problem. It is caused by changes in the MacOS 'Save' dialog box, introduced in MacOS Catalina. If you run the same version of Photoshop on MacOS Mohave then everything works as expected. Yes, it's taking far too long. But for you and me it is impossible to say what would be a reasonable time to fix this and what is no longer reasonable.
Could you then explain why this is not a problem with Illustrator, InDesign, etc. on Catalina?
It has to do with special routines that Adobe built into the Save as dialog in Photoshop, to avoid people losing their work when they try to save a layered file or a 16 bits/color file as jpeg (which does not support layers or 16 bits color). Apple removed the API that Adobe used for this in Catalina. Illustrator and InDesign are not affected because they do not have these formatting dangers and so they don't have these routines built into their Save as dialog.
139
Replies
AdChoices