Comments on: DotNetNuke Modules – Finding The Page a Module is On

By: Dave

Dave — Wed, 17 Sep 2008 00:16:22 +0000

Without running I’d have to say no only because it looks like really old syntax if it worked at all.

By: Ant

Ant — Tue, 16 Sep 2008 23:38:54 +0000

Private Function GetFirstModuleTabId(ByVal PortalId As Integer, ByVal moduleName As String) As Integer
Dim objModuleController As DotNetNuke.Entities.Modules.ModuleController = New ModuleController()
Dim moduleList As ArrayList = objModuleController.GetModulesByDefinition(PortalId, moduleName)

For Each modInfo As ModuleInfo In moduleList
Return modInfo.TabID
Next
Return 0
End Function

By: Ant

Ant — Tue, 16 Sep 2008 23:37:59 +0000

Will it be better if we do this?

Dim objModuleController As DotNetNuke.Entities.Modules.ModuleController = New ModuleController()
Dim moduleList As ArrayList = objModuleController.GetModulesByDefinition(PortalId, moduleName)
For Each modInfo As ModuleInfo In moduleList
‘Return modInfo.TabID
Next

By: Dave

Dave — Tue, 16 Sep 2008 16:38:24 +0000

Yes, it is (was).

As is common with most of my post I only gave you the specifics on how to retrieve the information. I did not tell you what to do with it.

IF you need to find out where a module is, this is how you do it. And even if you use this method, you wouldn’t retrieve it every time you hit the page because even on a relatively small site, you’d get killed on performance.

By: Néstor Sánchez

Néstor Sánchez — Tue, 16 Sep 2008 16:29:39 +0000

The tab iteration on a portal with thousands of pages will be quite expensive. A better solution from an architectural point is that the Checkout module saves its location to the DB, either by way of a module setting or a specific field in a module configuration table. In that manner, your other modules can retrieve this directly.