I have two repositories on two separate pages on my portal.  Each hosts a different type of content.  I I put up and populated the first repository without problems but did not assign any attributes.  I also made some modifications to the provided "directory" template to display my content.  No problem.  All worked well.

For the second repository, I wanted some attributes so I created the repository, added the attributes, and set the repository skin to the same template as the first repository.  After populating, I didn't see attribute selections initially so I looked in the documentation and saw that the attribute selection boxes have to be added to the template.  Not considering the impact on the first repository, I added the attribute token to the header template.

But when I looked back at my first repository, it seemed that all my previously uploaded files had disappeared!  Upon investigation, I determined that attribute selections made in the second repository were being applied to the first.  My first thought was that because the attribute selection was in the header template, that the first repository was trying to apply those filters and since those files did not have those attributes applied, no match was found.  So I created a new template without the attribute selections in the header, reapplied it to the first repository, but still no luck.  Any time I make an attribute selection in the second repositry, the file list in the first repository is filtered donw to none.  The only way I can get the files to reappear in the first repository is to go back to the second one and clear all attribute selections.

Any help or suggestions?

Thanks.

I added a new repository on the second page.  The repository ID's on my two modules are 382 and 389 respectively.  382 does not include attributes, 389 does.  I have run a SQL Trace while interacting with the repositories and note that if I set an attirbute on module 389, when I then go to repository 382, the gmGetRepositoryObjects stored procedure gets passed a value in the Attributes parameter that equals the attribute ID seleted in 382, even though there are no parameters associated with that module.  It's as if the attribute selection from the interaction with moduel 382 is being cached and reattached to module 389.  The only way to clear the attribute value out of the Attributes parameter on the stored proc when querying module 389 is to go back to module 382, set the attribute selections to All, then revisit module 389.  Then the SQL Trace shows that the Attribute parameter for gmGetRepositoryObjects is empty and the filter is not applied.

Thanks Steve.  I'll look forward to the update.  I love this capability by the way!  One of the reasons I avoided DNN in the past was because I needed to provide on-line library type capabilities for several different types of materials and formats.  And the core Links and Documents modules just wouldn't hack it.  I then looked at using a plug in forum module like ActiveForums and that was OK but still not quite what I wanted - to many steps for a user to have to drill down through to find what they were looking for and the basic form still looked too much like a discussion forum and not an on-line library.

When I found the repository module, I felt like I'd struck gold!  I've really enjoyed playing around with the templates and creating my own look and feel for my users.  One thing I'd like to see is the ability to designate either a file or URL within the same template because I have some repository sections that may include links to either a file or URL.  I found if I set up the template for a basic file upload that I can back door the URL into the repository table and that works fine so I'm content for now to do that when I have mixed content.  And maybe there is a template arrangement I haven't considered yet that will let me select either a file or URL as my target info.

Anyway, great job on this.  Exactly what I needed.  I'll remove the attribute selections for now and keep checking for the update.