5 Answers, 1 is accepted
0
Hi Katyusca,
This is not a common scenario - if you are allowed to create new folders, you should be able to upload files too. The RadFileExplorer control does not support such functionality, but if you want, you could override the StoreFile procedure so the users will not be able to upload files. More information on the subject is available here:
http://www.telerik.com/help/aspnet-ajax/radfileexplorer-custom-filebrowsercontentprovider.html
Sincerely yours,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
This is not a common scenario - if you are allowed to create new folders, you should be able to upload files too. The RadFileExplorer control does not support such functionality, but if you want, you could override the StoreFile procedure so the users will not be able to upload files. More information on the subject is available here:
http://www.telerik.com/help/aspnet-ajax/radfileexplorer-custom-filebrowsercontentprovider.html
Sincerely yours,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Katyusca
Top achievements
Rank 1
Rank 1
answered on 21 Aug 2009, 02:12 PM
Thanks so much for help.
I make visible=False the button and that works, but now i have some doubts about how really fileexplorer works, because i can see than make double postback (maybe cause it have a tree and a grid), but in a moment all element exits in the session is been clean. Why it could be?
I make visible=False the button and that works, but now i have some doubts about how really fileexplorer works, because i can see than make double postback (maybe cause it have a tree and a grid), but in a moment all element exits in the session is been clean. Why it could be?
0
Hi Katyusca,
We are aware of double-postback behavior in the older version and we already fixed it in the newest one - Q2 2009. Please update your project and you should no longer experience this problem.
Sincerely yours,
Fiko
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
We are aware of double-postback behavior in the older version and we already fixed it in the newest one - Q2 2009. Please update your project and you should no longer experience this problem.
Sincerely yours,
Fiko
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Jim Little
Top achievements
Rank 1
Rank 1
answered on 19 Jan 2010, 04:29 AM
Georgi Tunev:
I love the FileExplorer control but, with all due respect (and please accept my apologies in advance for the criticism), you are thinking about this issue the wrong way. I don't know if it's fair to say that is or is not a "common scenario" to allow new folders but NOT uploads. This thinking is a bit arrogant, in my opinion, because it essentially locks users into using Telerik's RadUpload product if they want offer the new folder feature in FileExplorer (I was able to turn that off but instead of setting the properties for allowing new folders to true and allowing uploads to false, I had to go through HELLISH programming to figure out how to change toolbars and context menus, which is not so fun for the newbie).
I happen to use ComponentArt's Upload control because I think it is far superior to Telerik's (which, among many other gripes, has all kinds of trouble canceling a request once a download has started). I think Telerik should realize when it designs and publishes controls that there really aren't many "common scenarios" and that developers are very often mixing-and-matching components to suit their specific needs. To assume that a developer is going to use ONLY Telerik components with a particular Telerik control is rather shortsighted.
I do hope Telerik continues to enhance this fine FileManager component by exposing more properties to turn on and off certain behaviors without the wrong assumptions about which features should be "automagically" activated when another feature has been activated (as is the case with new folder and file uploads).
Thank you,
Jim
I love the FileExplorer control but, with all due respect (and please accept my apologies in advance for the criticism), you are thinking about this issue the wrong way. I don't know if it's fair to say that is or is not a "common scenario" to allow new folders but NOT uploads. This thinking is a bit arrogant, in my opinion, because it essentially locks users into using Telerik's RadUpload product if they want offer the new folder feature in FileExplorer (I was able to turn that off but instead of setting the properties for allowing new folders to true and allowing uploads to false, I had to go through HELLISH programming to figure out how to change toolbars and context menus, which is not so fun for the newbie).
I happen to use ComponentArt's Upload control because I think it is far superior to Telerik's (which, among many other gripes, has all kinds of trouble canceling a request once a download has started). I think Telerik should realize when it designs and publishes controls that there really aren't many "common scenarios" and that developers are very often mixing-and-matching components to suit their specific needs. To assume that a developer is going to use ONLY Telerik components with a particular Telerik control is rather shortsighted.
I do hope Telerik continues to enhance this fine FileManager component by exposing more properties to turn on and off certain behaviors without the wrong assumptions about which features should be "automagically" activated when another feature has been activated (as is the case with new folder and file uploads).
Thank you,
Jim
0
Hi Jim,
The design of the implemented security model of the RadFileExplorer control is very similar to the model that is used in the Windows operations system. A very common scenario is to set only read permission to a folder and expect that creation of a new folder or file to be restricted inside that folder. We provide, however, the flexibility to implement your custom security model by developing a new FileBrowserContentProvider.
If you need to have permissions to create a new folder, but want to hide the upload commands, then I recommend you set the UploadPaths properties to the folder(s) where you need to create files. Then you can completely hide the Upload command from the RadFileExplorer's interface by using this approach. After doing this you will be able to create new folders but the upload will be completely disabled from the RadFileExplorer's interface.
I hope this helps.
Greetings,
Fiko
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
The design of the implemented security model of the RadFileExplorer control is very similar to the model that is used in the Windows operations system. A very common scenario is to set only read permission to a folder and expect that creation of a new folder or file to be restricted inside that folder. We provide, however, the flexibility to implement your custom security model by developing a new FileBrowserContentProvider.
If you need to have permissions to create a new folder, but want to hide the upload commands, then I recommend you set the UploadPaths properties to the folder(s) where you need to create files. Then you can completely hide the Upload command from the RadFileExplorer's interface by using this approach. After doing this you will be able to create new folders but the upload will be completely disabled from the RadFileExplorer's interface.
I hope this helps.
Greetings,
Fiko
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.