I have spent the last couple weeks browsing the forums and can't find a thread addressing this issue so I apologize if this is already solved.

We have a strange situation with the repository module.  One of the content managers "lost" the module that was installed on a page.  It is not visible anywhere on the page, even under the superuser account, isn't in the recycle bin, but the module usage page shows that it is still installed on the page.

When the dashboard module is installed on that page it shows 35 files and all the catagories.  However when you click on any catagory there is a postback with no change on the page.

The files are all still in the repository directory but installing a new instance of the module does not "link" into the files or tie to the dashboard.

Of course we could just delete all the files and start over but that is a lot of work and frankly I am concerned that the module will end up on a milk carton again.  ;-)

Ideas?

Haven't heard of anyone having this problem.  I'm afraid it will just take a lot of digging through the db on your part to see what's happening.

I would start by checking the event log, see if an error is happening when the module is being injected (although usually you would see an error on the screen). Then start digging through the tables in the db. Look at the Module Definitions table, the modules tables, the repository tables, etc, looking for abnormalities or bad or missing data that might cause the module to not appear.  You could also look at the web page source and see if anything is being generated on output or if the container is just blank.

You said the physical files are still there, look in the grm_repositoryobjects table to see if the data records are still there.  If so, to move files from one repository module to another is just a matter of changing the moduleid in the grm_repositoryobjects table to point to the new module.  So you could move all of the existing items to a new module and see if that works, saving you the time of re-uploading and re-keying your items.

But you are correct to be concerned, there is obviously something wrong and I would try really hard to figure our what is going on. What version of DNN and what version of the Repository module are you using?  You could try upgrading to the latest dev build (3.05.00) and see if that helps.  If you are a developer, or have developer resources, you could install the source version on a local dev machine, point the db to the site with the problem and debug it to see if the module is getting loaded by the core code and if so, what is happening in the module.

---

Steve Fabian e: steve.fabian@gooddogs.com w: http://www.gooddogs.com