The last version had the ability to create and point to a folder.  Example: Repository > Video.

I see that feature is no longer available. I am a bit concerned about existing instances of Repository that I had used this feature on. As well as wanting to know the reasoning behind removing folder selection.

TIA
Buck

I can see your reasoning form a top security level. But, I must ask you this question:

How many times will a host that has 50 portals running on a DNN instance going to be aware or be called on to set this up for a admin?

The logic behind this change is sound for a one portal DNN instance.

The way it is now, you are, without host intervention, forced to dump the contents of a new module instance into the repository folder. I could tell you a hundred reasons why, as admin, that I don't want to set a general write privilege to all users or all registered users on the repository folder. It was perfect before because you could define the custom folder write permissions to a specific group. Am I missing something?  I have not added a file to this newly created module instance yet. By default, will it create a numbered folder instance under repository or do files just get dumped into the repository folder? IMHO - Sometimes you need to trust and/or train the admin ...

TIA
Buck

I understand where you're coming from as well. After the release of 3.1.6 there were a number of posts asking that the feature be removed and/or hidden so Steve did so.

If you've "Store in users folder" checkmarked then the files will be in Repository\UserID (or possibly Username, I'm not on a computer that I can verify the sub directory name). Otherwise they'll just be in the Repository directory. Having all the files pointing to one directory should not cause any problems as the files get renamed when they are uploaded so even if the same user uploads the same file to the same spot the chances that the names will be the same are very slim.