Inspiring

Answered

"Export Save for Web (Legacy)" no longer working

Forum|Forum|5 years ago
March 14, 2021
5 replies
7797 views

Was upgraded to Photoshop 22.3.0 a couple of days ago & now can no longer "Export Save for Web (Legacy)". Every time I try, a popup error box says "This operation can not be completed.". I am running Windows 10. I have tried to research this online & have not been able to find an answer that works for me. Help!

Problem or error

This topic has been closed for replies.

Correct answer Akash Sharma

Hi there,

This issue should be fixed in the Photoshop 22.3.1 update that went live today. This update includes fixes to some of the top customer reported issues among other bug fixes. See Bug fixes and security updates

To update Photoshop to 22.3.1, click "Update" in the Creative Cloud desktop app next to Photoshop. See: More detailed instructions for updating

Let us know how it goes.

Thanks,

Akash

Akash SharmaCorrect answer

Legend

Hi there,

This issue should be fixed in the Photoshop 22.3.1 update that went live today. This update includes fixes to some of the top customer reported issues among other bug fixes. See Bug fixes and security updates

To update Photoshop to 22.3.1, click "Update" in the Creative Cloud desktop app next to Photoshop. See: More detailed instructions for updating

Let us know how it goes.

Thanks,

Akash

F

fafa5EAD

Participant

Anyone can help me to fix this issue. Save for web (legacy) can't be clicked

BrettN

Community Manager

Brett, please consider all of the actions and scripts that rely on Save for Web (Legacy). Please take this into account to ensure that if you will replace the legacy option, that in the "feature parity" is the ability for actions to record all parameters and for the Photoshop DOM to support this and for the ScriptingListener plug-in to also support this. If the legacy option was no longer an option, all of the scripts and actions would be broken, so there would have to be a way to easily "update" existing code or actions to use the new method.

Perhaps it would just be better to "hide" the legacy options from the interface, but still keep the underlying code so that old actions or scripts would not be broken, however, when creating new actions or scripts that the new feature would be forefront. As Adobe have been doing, perhaps a prefs option to make the hidden legacy options visible if neeeded would be the best balance.

We're still a ways out before this will be accomplished, so we don't know exactly how things will pan out. But, just like we have kept the old version of Export As as a "hidden" legacy item for a bit, we would certainly do the same for Save for Web once we do reach feature parity. However, my guess is we'd eventually want to remove Save for Web just to clean up Photoshop's code base. Keeping around old features like this creates bloat as we have to retain old API's that might not be used anywhere else in Photoshop and also rely on old OS and hardware standards. This is certainly the case with the old Export As (we are trying to deprecate the dependant features so we can eventually remove CEP and Generator). Luckily, my team, which is upgrading Export As, is also the one developing the DOM, so we'll be able to manage a smooth transfer of old commands to new ones. We always keep in mind how changes can affect workflows. Sometimes we can't avoid them (due to OS and hardware changes), but we mitigate things when we can. This will likely be a case where we can. More news as things develop.

pixxxelschubser

Community Expert

Works for me without problem with PS 22.3.0 Win 10

L

Linwood Ferguson

Known Participant

Same problem here, it will occasionally appear to finish, but just sits there apparently hung. It's much more capable normally than the new export options and I use it a lot. Well, I did. The little hint to use the other at the top is frankly more annoying than helpful since you can't actually aport it. Right now I'm going to lose 30 minutes of editing if I abort it, so hoping it will eventually come up and work.

If I were the suspicious type I would think this was motivational slow down. 😞

E

eyeland99Author

Inspiring

Sounds like a different result than mine. I get an immediate popup error message, no hang.

L

Linwood Ferguson

Known Participant

Interesting, mine this time seemed forever, I just killed it after 20 minutes or so (and lost my edits). A couple days ago used it and it finally came up after maybe 10 minutes of churning for the initial display. I did an export as and it worked, but that is SOOO limited in comparison, notably as mentioned it doesn't seem to do gif's, which is why I often drop into photoshop.