Skip to main content
davidt64328623
Participating Frequently
January 22, 2024
Question

Save for Web - Figuring out what breaks it

  • January 22, 2024
  • 13 replies
  • 5324 views

Hello,
I have been trying to figure out what breaks save for web in Photoshop on Mac, our designers are used to this feature for saving slices, and apparrantly "export as" doesn't offer the same functionality for slices.

 

You may have seen the error "Could not complete this operation. A write permissions error has occurred" when trying to save a file when using Save for Web (Legacy)

I know in 2021 people had issues with DropBox - this system doesn't have Drop Box, but it does have OneDrive - I don't think it's related as even with OneDrive syncing and everything it was working. 

The good news is I have figured out at what point Save for Web breaks - if you uninstall Photoshop and re-install from the CC app as a non-admin it basically stops working after that, so maybe even when Photoshop updates as a non-admin user it will likely break as well. 


Unfortunetly I can't seem to find a way to fix it. I've tried re-installing CC and Photoshop after changing the non-admin to an admin account, re-installing on the original admin account. I checked all the security options, it doesn't seem to matter what access you give to Photoshop it simply won't work anymore.

The last thing I tried was create a new non-admin profile on the Mac, logged back into CC - and Save for Web works on that profile. 

So does this basically means something breaks in the profile and even re-installing won't fix it. It would be good to figure out what is broken in the profile or how to fix it. Anyone got any advice?


I checked this, it seems the original broken file has these permissions.
https://helpx.adobe.com/photoshop/kb/required-permissions-for-photoshop0.html#:~:text=When%20running%20Photoshop%20from%20a%20non-Administrator%20account%2C%20Photoshop,with%20full%20administrative%20rights%20is%20required%20for%20installation.

This topic has been closed for replies.

13 replies

davidt64328623
Participating Frequently
January 30, 2024

@Kevin Stohlmeyer Yes it seems to work again if unlink oneDrive (this also causes onedrive to log out and close) if I just close OneDrive without unlinking then I can't use Save for Web. In my other user profile (for testing purposes) I have onedrive enabled, I can save for web no problems at all. It's very strange.

I just re-linked oneDrive and it's all working and saving again as you would except to OneDrive with no errors, but I know it's only a mater of time before it breaks again. I'd love to figure out what is causing it to break.


I think this has to do with which folder it defaults to for saving somehow while using Save for Web, and maybe alias folders plays into this as well, which would explain why people are having problems with DropBox and other syncing services. I'll have to think of some more tests for this theory. 

The problem is our org is hugely dependent on OneDrive, that isn't going to magically just stop being used here,  and some of our designers are very dependent on Save for Web. 

Kevin Stohlmeyer
Community Expert
Community Expert
January 29, 2024

@davidt64328623 are you able to remove OneDrive completely on a test machine to see if this resolves?

I tested on my Mac here (M2, OneDrive corporate account) and the error comes up with One Drive active.

If I log out and quit One Drive it works again. I'm not saving to the One Drive location either.

Legend
January 29, 2024

Is everything local? Files and save location? Does Photoshop have full disk access? You may just want to run with admin privileges anyway. Mac isn't really like Windows when it comes to account privs.

davidt64328623
Participating Frequently
January 29, 2024

Hi kevin stohlmeyer, I did try turning off OneDrive, unfortunetly that doesn't help. I had read your post in that thread months ago and had tried it againt recently with no luck. This has been an issue for a long time in our org.

Kevin Stohlmeyer
Community Expert
Community Expert
January 25, 2024

To be clear - this has to do with a OneDrive update that broke this feature. Something with the sync is still affecting the entire HD not just the sync folder.

Kevin Stohlmeyer
Community Expert
Community Expert
January 25, 2024

@davidt64328623 One Drive has been well documented in this forum specifically for the situation you are describing. Turn off One Drive syncing and try Save for Web.

Legend
January 25, 2024

I do product photography and every one of my output files goes through Save for Web, to the tune of thousands. I've had numerous issues along the way but SfW has always been rock solid. I'm just saying, people want to use files on a cloud service and its not reliable. Local files should be fine.

davidt64328623
Participating Frequently
January 25, 2024

If the file is in a non-onedrive folder (like downloads) and you save to downloads, and you still have the same error, then what? You aren't allowed to have any cloud storage on your device at all ?

Legend
January 25, 2024

DO NOT USE CLOUD SERVICES WITH ADOBE APPS.

They usually work until they fail and then everyone is confused. ONLY ONLY ONLY work on local files.

davidt64328623
Participating Frequently
January 25, 2024

It seems to me it has something to do with OneDrive, but not necessarily OneDrive that is causing the issues. 
Breaking it initially was triggered by uninstalling/re-installing Photoshop - OneDrive was functiong with it fine at the time.
On the second profile, it was broken after setting up oneDrive on the new profile.

It seems to not matter if the file you are working on, or the location you are saving to is in OneDrive or not.
On the second profile, after it was broken, I tried navigating to the downloads folder, via the Mac HD, suddenly it started working again. I could save to OneDrive folders and non-OneDrive folders again.

I tried to re-produce this on another Mac that is having the Save for Web problem but before I had a chance to try Save for Web was working. 
Now 2 days later, it's not working again for that user, so we re-produced what 'fixed' it for me, but no luck. 
I'm not sure what the pattern is here.