aoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.orgaoec.org

Getting the REAL Module Settings!

Strangely – since we upgraded our directory websites (such as http://www.foremosthunting.com and http://www.foremostbrewing.com) to the newest DotNetNuke version (5.02.01) our custom site map wasn’t working anymore.  I am using theiFinity.DNN.GoogleSiteMapProvider – a wonderful FREE provider – to create my site maps dynamically.

Within my directory module – I was originally using ModuleSettings to save the settings.  As our requirements grew – I knew I needed to switch over to TabModuleSettings to store my settings.  I just now came to the realization that while most of the directory listings were showing up fine for Foremost Hunting; my homebrewers website Foremost Brewing – wasn’t showing my homebrewing related listings.

Low – and – behold – when you have a question about DotNetNuke – review the core source code and see what the Core Team did.  I followed through the PortalModuleBase and found the settings (both ModuleSettings & TabModuleSettings) were being gathered in the DotNetNuke.UI.Modules ModuleInstanceContext – which was my solution for fixing my directory module’s site map provider!

Leave a Reply