Wed, Oct 23, 2019 4:10 PM
8 h ago
3 m ago
so as you know (hopefully) you have been having an issue with photoshop when you take a psd file with layers and work on it and then save a jpeg or any other file format you get the first time a file example file name (name.jpg) this would be from your master file with the layers in it (name.psd) then when you get a change or have to update something in the layer you then save it which (name.psd) done . it saved over the file. the issue comes when you save the other file format jpeg in this instance you would get (name copy.jpg) not overwriting the file name even when prompted to do so ? and now I just found a real funny. when saving that same file you would have name.psd and name.jpg and then name copy.jpg so when I went back to the psd file to update it again and I am saving this test all on my desktop (it happens on the external as well) it actually does overwrite the file but guess which one of the three files LOL the one that says copy ..... so your software does do it just not on the original file save as. you can pay me later for finding the spot where you need to code better and fix it already .
2 m ago
I should really unsubscribe from this thread, but somehow I enjoy witnessing the ever-more-pathetic failure of Adobe and its software-rental rip-off.
Everyone: Shitcan Adobe and buy competing apps. But continue to harangue Adobe in this thread just to see how shameless and inept they can be.
Yes...Adobe still thinks it has a total monopoly in this section.But there are plenty of good alternatives meanwhile like davinci resolve for video-editing or affinity-suite.I`m looking forward for the day, when adobe wakes up and realises that their stupid rental-method, their miserable updates/broken apps and policies backfired in long term.Sadly, I´m still dependent on some of their apps.But the day will come. And I´m sad about it, because adobe had some pretty decent apps back in the days. The days where UPdates fixed stuff and didn`t cause more problems...
Resolve and Affinity both suffer from major UI defects... but probably no worse than Adobe's, and at much lower prices.
Plus, Adobe insults its customers by abolishing its support and replacing its bug-reporting mechanism with this insulting and pathetic forum.
Hey Adobe, vote THIS up... right up your ass.
Come on … it must be obvious to you that you are violating the Forum Guidelines (no matter how justified your frustration about the bug fixing performance of various Adobe product teams may be).
To whom and what are you talking about?
We are latest version of Photoshop, MacOs Big Sur, its been happening for at least the last 3-4 minor updates of Adobe Photoshop's releases in recent months. Its so annoying. Have to go into root of files of directories every time and delete the old, take off the word copy, then update links manually in both Illustrator and InDesign.
@Aidan Clarke this idiotic bug has been around since late 2019. What’s maddening: it’s a fundamental computer function ie save/replace we’re complaining about. Simply mind boggling Adobe acts like the current function is the new normal. 🤦🏻♂️🤦🏻♂️🤦🏻♂️🤦🏻♂️
Unbelievable that we're still discussing this.
Agreed, I don't understand their reasoning for adding this "feature". Because, it seems like this is the way Adobe wants it to be... No way save/replace would go undetected for multiple years if it weren't on purpose. No way.
I switched over to Windows a few months back and the "Save As" --> "Replace" does exactly what one would expect it to.... for the last 25+years of computing.
Sorry to hear this is STILL happening on Mac. :(
This issue is related to Mac OS Catalina and Big Sur. I am on Mac OS Mojave and have zero issue on this.
While it occurs on Catalina and Big Sur lets be careful about how we word this. This is not a MacOS issue that Apple needs to address. This is an Adobe issue that Adobe needs to address. They have figured out how to have this same issue work just fine on their other products we just can't seem to get it resolved in Photoshop.
Agree. All other Adobe applications work fine on Mac except Photoshop. I think it was that "Uh oh" moment for Photoshop programmers when Catalina and Big Sur are paving the way for M1 Macs. Something must gone very wrong on the root level of Photoshop programming language. Perhaps Adobe may need to rewrite Photoshop from scratch for however long it takes to fix this issue.
The frustrating part, at least for me, is that Photoshop will correctly overwrite files in very specific circumstances. If the file is already flattened (no layers, no alpha) or the filename contains " copy" at the end, or if you use the (very slow) "Export As..." option (which only supports certain formats.)So even on Catalina and Big Sur, we know this "works" it just doesn't work in general.
I started using "export to as...jpg" instead of "save as" and it will save over the file, instead of as a copy. Hope this helps someone!
This option is working for me. Thank you!!!
1 m ago
Oh, OK. Most of us have been there before, believing it has finally been solved. I’m guessing you didn’t try to save as a layered file over an existing JPEG file. Because, if you do, it will add “copy” and not replace it. THIS is why so many of us are fed up with Adobe for not fixing this in a year and a half. Especially because Photoshop runs natively on a Silicon Mac now. Anyone who reads this thread tested this on one yet?
Charles, you can't save a layered .jpg under any circumstances. We're talking when you have a current .jpg saved, made modifications, then do a "save as" to replace the current file. Photoshop will save the file name with "copy" even though you get the "... already exists. Do you want to replace it?" message.
Now upon saying that. I did upgrade my Photoshop to 22.3.0, saved out 4 different files and at least for me the bug has been fixed.
I have updated to 22.3.0 and the bug has not been fixed. Steps to reproduce:
Did your files have layers?
Same as philip_wels. This f.... bug has not been fixed! Layers or not in the file, you should be able to replace it!
Lora, my wording was poor. Been making a living in PS for 31 years. Of COURSE I know you can't save a layered jpg. My point is you can't save over an existing jpg FROM a layered file without it adding "copy"
I've been in the industry just as long. Started with Photoshop version 1.
I did 4 tests saving over 4 different existing .jpgs from a layered file and I did not have "copy" in the title.
I'm running a Mac with Big Sur and Photoshop 22.3.0
Lora, are you opening a layered PSD file, then using the Save As ... menu to save a JPG file?
yes, as well as opening a .jpg, added layers then doing a save as. The .jpg didn't have copy in the title. Then if you want to save the layered file it has to be either a .tif or .psd
With all due respect, years or level of experience have no bearing on the existing bug. It's real, well-documented, and easy to replicate.
Hoping for a fix. This is beyond stale at this point.
Lora, did you then attempt to save over the existing JPG file? If so, you're the lone person who isn't affected by this bug. Please site your system configuration, PS version, etc. Thanks.
Lora, don't change the name when you are saving the file from a psd to a jpeg
Kudos. We've seen some stuff. I have to admit I've been burned by my Photoshop/Wacom driver/MacOS setup too many times with updates breaking something. I confess I haven't gone to Big Sur yet. If you haven't run into any issues, is it worth the risk for me?
Hi, chazcron. Other than the ongoing Photoshop bug, I haven't any issues with Big Sur. Cheers!
Thanks, Mattrock, I think I'll pull the trigger.
To date (over a year later), 6,200 views, 420 comments (and counting), yet Adobe reps remain clueless while a very basic software change remains unchanged. Welcome to the Adobe version of 21st century customer satisfaction and follow-up. 🙄
@2stepbay If I treated my customers like Adobe us, I would be bankrupt in no time.
I have 22.3.0. On Big Sur. It is not fixed.
I can also confirm it is not fixed for non-Silicon, PS 22.3.0, and Big Sur.
lora_c, Maybe you are just lucky.
Apologies if this has already been posted, but have been hunting for a fix for a long time and came across this - so far it's worked OK for me on Catalina 10.15.7 and Photoshop Elements 2021
With version 22.3. (March 2021) Adobe says it is fixed:
Fixed issues in Adobe Photoshop
But it is not!
Such a shame...
@Sendy Fiala I haven't updated yet. Will do so later. Is the save behavior the same as previously reported? If so, I wonder what Adobe thinks it fixed.
yes, it is exactly the same behaviour. I'm on Mac OS Big Sur. Some says that this is problem related to Mac operating system, but it isn't. Other apps don't do it. Even other apps within Adobe CC don't do it. Even Photoshop don't do it if you use Quick Export function (set up in Preferences, Export tab - you can change the filetype to JPEG). As I wrote elsewhere, Adobe is erratically patching their bugs, bringing the new ones along with each update. They should take their time, fix all bugs, carefully do beta testing and bring update two times a year max. Their behaviour results in situation, when proffesionals are scared of every single update.
Adobe are so hopeless. IT IS NOT FIXED!!!!!!!
It drives me so crazy!!!
It's not just Photoshop, it's Illustrator, and Dreamweaver
Still not fixed on 22.3.0
Now my simple question is: when will it be fixed?
PS: i'm going to ask for a refund on this.
Please do that too, we have to raise our voice.
I'll say it again... Broadcast that comment on Adobe's Twitter feed, maybe that will
get their attention?
Some people think that spraying graffiti on Hymnals is a form of communication. To the civilized part of the world it is simply destructive behavior.
Dgrainger back with more of his false equivalences & value judgements 🙄
@jh_b8ih8qyak6flq You must be one of those that think it appropriate!
Wrong. Do you ever tired of being on that high horse?
Hey gang. I hope I speak for everyone else subscribed to this thread (all 181 of us) but the back and forth bickering between individuals isn't helping anyone. Numerous times when I see this start up I ALMOST unsubscribe from this post and I wouldn't be surprised if others have. I stay subscribed for that ONE DAY when Adobe finally makes this a priority and we can mark this fixed and go about our lives. Sure we are all annoyed nearly a year and a half later but man, gotta say I appreciate the radio silence here when there is no news to report. If an update comes out and its still broke, news worthy but as a community here, if we can try not to chirp each other, the rest of us hanging out on the sidelines would appreciate it. Thank you!
I actually agree w u 100%. But I am tired of Dgrainger popping up making useless posts that take pointed jabs at ppl whenever anyone suggests blasting Adobe’s Twitter feed.
His false equivalences have ranged from divisively political to conspiratorial to rhetoric like his last comment, equating it to vandalism of religious objects. We get it, he doesn’t agree w/ “harassing” Adobe till we get action. But I’m over letting his useless inflammatory commentary slide.
agreed. really quite over the random notes about NOT a solution haha i can't believe they just keep rollin out the updates (more frequently than i remember with the last few versions) and still not a mention of this issue. did they really just kinda abandon this to focus on big sur/M macs or something? seems it.
Being one of the earlier posters regarding this infuriating issue, I find it incredible that Adobe is apparently ignoring the issue. What else can we assume, since Adobe hasn't provided any information as to why this happens, or if they are even considering fixing it. It is easily the single most annoying and time-wasting feature of what is a great program. Wipe this spot of mud off Photoshop, Adobe!!!
I don't work for Adobe, but I do know they are working on a fix. That's all I can say.
Johan W. Elzenga,
I have and that was last year and this year they (adobe) say the bug is fixed (it is not) I show them the proof and they bump it up the line and then close the issue.
@Johan_Elzenga I'm going to assume you have access to insider information you've agreed to keep secret. If that's the case I'm glad to hear this, though I'm still annoyed it's taken over a year and we're still waiting
@lora_cawkins_7886325 ... you do realize that the link you've posted takes you to this feedback forum?
oops no I didn't. sorry. I deleted it. duh
Thank you Frank. You're the first official poster here from Adobe. This thread dates back to October 2019. Seems there ought to be a more meaningful/direct way to engage Adobe rather than a thread that goes on for over 16 pages before anyone in an official capacity steps in. I appreciate this will be resolved!
ps I rolled back and it still does the same dame thing 21.2.6
How can we improve?
No tags available