Posted on Oct 28, 2008
(permalink)
That is not happening in my case. When I first create the editor, I'm setting the view path to ONE virtual dir, which is basically a recordType/ID. I'm not setting the delete or upload paths. The goal is that I don't want the user to be able to do ANYTHING at the root level. What I will display at the root level are two folders, one for all the global stuff and one for a local record specific workspace. If the user drills into the global, that is also only READ everywhere. No uploading or deleting. If they drill into the local workspace, they can upload and delete files.
NOWHERE do I want them to be able to create directories.
The custom provider is getting called and I'm returning the correct permissions settings for each DirectoryItem but it's not working as expected.
When the image manager first appears, both upload and new folder are enabled at the root level even though in the custom provider I'm only returned Read. Delete is correctly disabled. ResolveRootDirectoryTree is called for the single root virtual path I supplied and I'm returning PathPermissions.Read ONLY. When I walk the return value and check my child directories,my other virtual sub directories are there and their permissions are set correctly.
I even temporarily changed it to return only Read for all directories, even my workspace. Yet New Folder and Upload remain enabled everywhere.
The only thing that seems to be working properly is Delete.
Also, how can I remove the up directory '..' from the my initial display at load? Right now it's letting them go back up one directory. Interestingly, that directory does have everything properly disabled.