Hi everyone.

Is there a way to store module settings at portal level? I use Settings property of the PortalModuleBase class, but it is at module-instance level, different instances of module have get different settings collection.

If you need portal level settings - store the properties in portalsettings instead of modulesettings.

there is a shared method in DotNetNuke.Entities.Portal.PortalController called 

UpdatePortalSetting(ByVal portalID As Integer, ByVal settingName As String, ByVal settingValue As String, ByVal clearCache As Boolean)

that can be used to store values in the portal settings table - just be a little careful when choosing a settingName to make the value unique enough so as not to cause clashes with other potential users - "MyModule_SettingName"

And a complementary method to retrieve the values.

GetPortalSetting(ByVal settingName As String, ByVal portalID As Integer, ByVal defaultValue As String) As String

NOTE however - that this value may not be stored as expected if you create a module lvl export template - you would most like need to manually implement iPortable to ensure these values are exported with the module.

Westa

yes it is a way to make sure some value is returned -

Westa