I don't believe there is any ability to create custom portal settings.  What we typically do is to create Host Settings and then tack the portal number on to the end of the settings name.

Hope it helps,

---

Brian Dukes Engage Software St. Louis, MO 866-907-4002

DNN partner specializing in custom, enterprise DNN development.

The class DotNetNuke.Entities.Portals.PortalSettings provides two shared methods:

Public Shared Function GetSiteSetting(ByVal PortalId As Integer, ByVal SettingName As String) As String

Public Shared Sub UpdateSiteSetting(ByVal PortalId As Integer, ByVal SettingName As String, ByVal SettingValue As String)

which obtain the ModuleID of the specified portal's Site Settings module (which is supposed to have one and only one instance per portal) to then get and set entries in the ModuleSettings table.  I have never used these two methods preferring to create my own more strongly typed settings tables for this purpose if many settings are needed. If you should use the GetSiteSetting and UpdateSiteSetting methods you will need to be very careful to name your settings keys to avoid collisions with any core site settings and those of any developers. I would suggest something like: "CompanyName_SettingName" or "CompanyName_ModuleName_SettingName".

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner