There is a problem with this module when you place it on a "Child" portal in your DotNetNuke Intallation:

1. Create a child portal such as:  http://www.yourdomain.com/childportal.
2. Add a page to the child portal.
3. Make the page ONLY visible to "Registered Users".
4. Add the Download Module to the page.
5. Place a download in the module like a text file or zip or something.
6. Create a user (who ONLY exists in the child portal and NOT the parent portal).  Such as "testuser".
7. Login to the Child Portal as the "testuser".
8. Try to download the file.
9. You will be automatically taken to the DNN login page.

Why you ask?

Here's what I found:
The way DNN is built to handle child portals uses cookies, header values, and querystring to recognize which portal the user is logged into.  If you build a module that tries to access any .aspx page, then Global.asax will interpret the request and apply DNN security.  If DNN cannot determine which portal you are trying to access (either by cookie, header, or querystring), then it defaults to the parent portal in the request.

On the ASP.NET forums, suggestions are that you make your links include the following querystring parameters so that DNN can recognize which portal you are accessing:
tabid=<the tab(page) id>
pid=<the portalid>
mid=<the moduleid>

There are two parts in the Downloads Module that are causing the problem.

1. The thumbnail generator needs to use the tabid, pid, and mid parameters, or it will automatically log the user off.
2. The download link needs to use the tabid, pid, and mid parameters as well.

Thanks for your hard work, and I hope you have time to get this into a future build.  I am currently not able to use the Downloads module on any of my child portals because of this, so I have to resort to the original DNN "documents" module (which as you know is not nearly as robust as this module!).

-- Will G.