Breaking change regarding the files storage location

[stetard]

Describe the bug

After upgrade the module from 3.5.6 to 4.1.1, customized file downloads are using to a bad location.

Software Versions

• DNN: 09.13.00
• Module: 04.01.01

To Reproduce

Steps to reproduce the behavior:

1. Upgrade an old website using the 3.5.6 version to the 4.1.1
2. Click on the download link for a file listed by an existing module (created with the old version)
3. The error message is: [FileNotFoundException: Could not find file 'C:\Website\Portals\0\Repository...

Expected behavior

User should obtain the selected file when clicking on the download link.

Additional context

This problem occurs when the file storage location have been customized with an old Repository module version.
In this cas, the correct path is 'C:\Website\Portals\0\Download...' instead of the default ''C:\Website\Portals\0\Repository...'.

[stetard]

I'm wondering why the module settings doesn't allow anymore to use a specific folder to store the file.
Is this related to some security risks?

I think it could be better if the module accept some old customized locations and only block the personalisation for the new module instances.