I have developed a module that is to be used across several pages within my DNN portal.  It shows a list of webinars that one can register for or view depending on whether the webinar has already been recorded, or has not yet happened.  All of this functionality works quite well, but I have one issue.

In the settings control for this module, I allow the user to select an existing page within the portal.  This page is to be used as the "Detail" page for when a user clicks on the title of a webinar from the list.  I was originally using the Settings object, but after much reading, I modified the code to store the url for the detail page in the ModuleSettings object instead.  All other settings (for specific instances of the module) are being stored in the TabModuleSettings object.  My thought behind this is that I want all instances of the module across the entire portal to use the same detail page, but the other settings should be specific to an instance of the module.  For some reason, the detail page selected is not the same across all instances of the module in the portal.  Here is the assignment statement that is run when the settings are saved:

-----------------------

modules.UpdateModuleSetting(ModuleId, "WebinarDetailPage", PageDropDownList.SelectedItem.Value);

-----------------------

I was under the assumption that the ModuleSettings object would affect ALL instances of a module, and the TabModuleSettings object would only affect an instance of a module on a specific page.

I currently have two instances of this module on two separate pages.  I ran the following query on the DNN database to verify that everything was working correctly:

-----------------------

SELECT *
FROM dnn_ModuleSettings
WHERE SettingName = 'WebinarDetailPage'

-----------------------

This query returned TWO rows instead of one, and each instance of the module has its own unique ModuleID.

Shouldn't the ModuleId be the same across all instances of the module?  Is there something that I am missing here?

Chris,

First off, thanks for your quick response.  I ended up answering my own question earlier today when I ran across an article that mentioned exactly what you just explained.  My problem was that I was adding a new module each time I put it on a different page instead of copying an existing instance.

Most of the documentation and articles out there seem to suggest that as long as you use the ModuleSettings object it will apply to all instances of a module.  It seems a bit awkward that this strategy only works if you create the first instance and then copy it to other pages in order to create more.  Are there any plans in the future to implement a settings storage strategy that WOULD allow one to apply settings across all instances of a module regardless of how that module was added to portal pages?

Anyway, no use crying over spilled milk...my problem is solved, and again, I appreciate your quick reply.  On a side note, I thoroughly enjoyed your 25 part series on module development.  It was an excellent jumping off point for me when I first began working with DNN a few months back, and I look forward to seeing some more advanced topics in the future.

Cheers!