When they're set to complete that means they've been added to the code and tested that they work. However, in the case of REP-3092 I accidently duplicated that enhancement when I entered it so I set it to complete and added a comment that has the link to the original enhancement request. http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=2831.

Hi guys, it seems that thread compiles quite a few feature requests so I'll add mine. Some of them are already awaiting in Gemini, but that's just for a quick summary of what I feel important.

We're currently having our module downloads in a DNNPortal-Download module from Hans-Peter Schelian, which looks pretty much like a repository clone (I haven't checked, but it can't be that you guys did not share a code base), hasn't been maintained for long now, but still proposes the same kind of standards and additional features.

I'd like to move to the repository shortly, but I can see a few important features that I'll be losing:

• Per file download rights
• download auditing (does not have to be more than a simple standard LinkClick/AuditControl to start with)
• start/end date (which has been quoted above)

Now Hans-Peter is in charge with the blog module, which I guess does not leave me much time to keep up with his other free stuff, and the module is open-source, so I'm pretty sure he'll be happy to give you the pointers to import those functionalities from his code.

Then another featured mentioned here, which should be eased by DNN's latest version: DB storage is now supported natively, I haven't checked at the current repository plumbings with DNN files helper, it probably won't take long to implement if not already supported.

Content localization is also something, which I'd like to see (not there neither in DNNPortal-Download). There, I think that the reference is MMLinks, and I'm sure Mauricio Marquez, also project leader for the FCKEditorProvider can bring some help since MMLinks is a similar template based Link/Download module and pretty much everything in his module is fully localizable.

Finally, Versioning with Source-control/Sharepoint like features would definitely complement the Repository's current purpose, as stated in that post. Happily it's on the road map, and I think when all those are implemented, Repository will get into the first class together with Peter Donker's infamous Document Exchange Pro.

Sorry I can't help with the devs right now, but I'm sure you project guys can help making each other's life easier by sharing your early DNN contributions.

Cheers

I have another request for the Repository with respect to sub-categories.  It would be nice if a user could subscribe to the categories they are interested in.  So that when they log in the default items they would be presented would be in the list of items they subscribe to.  Obviously they would need a way to see all categories and filter as they can today.  It would also be nice if there was a way to rank the categories by user, for example a user could select a "Hot/Critical" category, "normal" category, and "do not show" category.  With the idea that they could then filter on the hot or "hot and normal" etc...  Possibly chaning the appearance by making the hot/critical backgroud red, anyway you get the idea.

Thanks.