With regard to file upload location, I had made a request early on in the old forums, but cannot find the post for reference.

What I would like to see is a file repository location defined by the administrator, rather than having it forced under the DNN portal folder structure. For example, the repository could be on another local drive, file share with UNC path, or even the database.

If you had a global setting for the repository, one that affected all modules in the portal, then you could still use your current subfolder structure under the adminstrator defined root path.

Bottom line, is I would like to see the files better protected by moving them out of the portal folder structure, as well as letting the admin determine where the best storage location is since the data requirements can grow quite large.

Also, because of the current storage scheme, even when a LiveContent module has controlled access via security roles, the URL to a specific picture allows annonymous access.

Of course, your proposed desktop application for user uploads would then need to handle the above situation without the need to give users read/write access to the repository location.

Rob Ralston