Okay, that makes sense. I'm going to have to read the documentation cover-to-cover to see what else I missed, as skimming through it didn't divulge that information.
1. Once I got the right template up there where they could upload again, the newly uploaded files had the pencil icon available to them. The previous ones they had uploaded still don't allow editing. I'm assuming the database has a display name entered instead of username (or something like that). In any case, this limitation is going to be a pain. Is there a way you can allow a security role to edit existing repository entries?
2. I switched it to the default template, then had them try uploading. There was still a "Resource URL" option. So, I switched it to the Nifty temple, and the file upload box showed up. Later, I ran some tests on another portal, and it was working like it was supposed to. So I went back to the original Repository and switched it back to the default template. This time it worked... Go figure....
3. Cool, that worked, wasn't looking for it there!
Now if I could get all the other DNNDownload modules converted, I'd be set. You sent me a script to move them over awhile back, but I never used it. Testing of the GoodDogs Repository at the time showed some limititations and I was instructed not to move them until the Repository was more evolved (which I think it is ready now).