Dot Net Nuke is maturing and as such is being used on larger and larger installations.  As we all know the bigger your portal the more files you have associated with it.  The current File Manager system places all of your uploaded files into the one directory.

http://www.dotnetnuke.com/Portals/0 

which leads to an administrative headache once you add a reasonable number of files to your portal.

The new Advanced File Manager project is addressing this limitation by enabling site and host administrators the ability to create/edit and delete folders into which they can upload, download, delete and rename files.

Site administrators will have access to their own Portal Folder such as Portals/0.

Host administrator will be able to gain access to all folders on their installation to do administratove maintenance like deleting old directories and cleaning up after a failed module installtion.

1)  The File Manager should allow the user to fully manage (add, update, delete, move, copy) directory structures.  This capability should be restricted to working within a designated directory that is determined by the user role.  Host accounts should be able to manage all directories within the virtuadl directory.  Portal administrators should be restricted to the portal folder to which they have admin rights.

2)  The File Manager should allow the user to navigate using either a directory tree (like windows explorer) or using a single folder navigation interface.

3)  File selection dropdown lists should allow the user to navigate the directory structure and select the appropriate file or folder.  This will be done with a small cut down version of the file manager that just allows navigation and selection of the file.

Joe Brinkman did a lot of work on this module for Version 1.0.10 as can be seen here http://theaccidentalgeek.com/DesktopDefault.aspx?tabid=34.  Jow has donated his work to the DNN project which means that it has ended up in my hands :)

So far I have changed all of the name spaces to DotNetNuke and have it running locally.  Here is what it looks like so far.

Next step is to make the folders and files role specific.