You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is regarding the following enhancement that was added in 2.6
[Feature] Marking write-only and non-accessible directories with special icon as in Finder.app
I work for a university and we run an FTP Server using Gene6 FTP Server 3.8 on Windows Server 2003, we are using Active Directory/NTFS permissions to manage users and user permissions, so Unix CHMOD permissions do not apply at all.
Starting with Cyberduck 2.6 which added the marking of write-only and non-accessible folders.
It displays a red icon(which I presume to be the one for non-writable folders) on every folder, even if the user actually has full read and write permissions. This bug doesn't actually prevent the user from writing to the folder. It does however confuse our students, so we were forced to go back to 2.5.5.
Would it be possible to have an option to completely turn off the marking completely and revert it back to the way 2.5.5 did things, atleast until the permission detection works properly.
Thanks,
The text was updated successfully, but these errors were encountered:
Hi,
This is regarding the following enhancement that was added in 2.6
[Feature] Marking write-only and non-accessible directories with special icon as in Finder.app
I work for a university and we run an FTP Server using Gene6 FTP Server 3.8 on Windows Server 2003, we are using Active Directory/NTFS permissions to manage users and user permissions, so Unix CHMOD permissions do not apply at all.
Starting with Cyberduck 2.6 which added the marking of write-only and non-accessible folders.
It displays a red icon(which I presume to be the one for non-writable folders) on every folder, even if the user actually has full read and write permissions. This bug doesn't actually prevent the user from writing to the folder. It does however confuse our students, so we were forced to go back to 2.5.5.
Would it be possible to have an option to completely turn off the marking completely and revert it back to the way 2.5.5 did things, atleast until the permission detection works properly.
Thanks,
The text was updated successfully, but these errors were encountered: