In this video we’ll cover some of the major upgrades. I do hope that this is solved in the next release of Photoshop.Photoshop CC 2015.5 June 2016 release 100% Free Download Adobe Photoshop CC 2015.5 for Mac OS Download Link: bit.ly/PSCC2015_5_Mac Subscribe + Like + Share + Comment = More Video Tutorials! Thank you for watching! The 2015.5 release of Photoshop CC rolls out exciting new features for designers and digital photographers. I am aware that you can change the POSIX after the fact and modify the umask to 002 but at the same time I shouldn't have to mess around with file system permissions to get Photoshop to work correclty in a shared storage environment. Many people utilize ACLs in their shared storage environments for various reasons (like Premiere coming up with it's own POSIX permissions and zip files) and Photoshop ignoring those ACLs will cause problems. In my eyes (and the client's eyes) this is a major issue. I then changed the POSIX permissions and verified that ACLs were being ignored. I also verified this on my own system running 2015.5 and found that when I created a new PSD file in a folder with ACLs the ACLs were not inherited by the PSD file. This allowed the user to save the file which had been created by another user. I verified it was only looking at POSIX by modifying the POSIX permissions on a test file (opened it to rwx-rw-r-) so that the group could write the file. POSIX on OS X are restricted to Owner R/W by default so this quickly became a problem. In looking into the issue I found that even though the ACLs were correct on the filesystem Photoshop was completely ignoring them and was defaulting to the POSIX permissions. They were no longer able to save PSDs that other users had created.
They recently updated to Photoshop 2015.5 and immediately started having permission issues with PSD files. The client has a SAN that uses ACLs to control permissions due to having multiple AD groups in use. According to the client the issue did not exist on 2015.4 I wanted to submit a bug report after running into this issue with a client and confirming it on my own system.
0 kommentar(er)
