Geeks With Blogs

News My Blog has been MOVED to https://mfreidge.wordpress.com

Michael Freidgeim's OLD Blog My Blog has been MOVED to https://mfreidge.wordpress.com

Current version of DNN(4.0.2) doesn't support multiple module definitions when importing templates

The issues are listed on DNN support site. By some reason comments for the issue are not allowed.

So I will post here  my suggestion how to resolve problem 3 (the imported result the page will contain duplicate modules, one for each moduledefinition).

DNN portal Template XML has <definition> element in the section.

However it does saves ModuleName instead of ModuleDef.Name.

To fix a problem the ModuleDefinition name should be saved in the <definition> element (Is it logical?)

The change should be done in  \admin\Portal\Template.ascx.vb, function SerializeTabs, line ~ 464.

The similar change should be done in \DNNLibrary\Components\Portal\PortalController.vb function ParsePanes, , line ~1288. The code should call ModuleController.GetModuleByDefinition.

Module Definition names are expected to be unique, so there is no need to store combination of DesktopModule name and ModuleDefinition names  in the template.

Note that it will be  a breaking change, because old templates will use Module names instead of Module Definition name.
It will be required to change XML version and have code branches to support both old a new templates.

Consider that it is not a simple change, I desided not to implement it in my local DNN, but just split modules with multiple module definitions into separate modules.

I hope that future versions of DNN will address the issue.

Posted on Friday, February 17, 2006 6:25 AM DotNetNuke | Back to top


Comments on this post: Support of multiple module definitions in DotNetNuke import/install.

# re: Support of multiple module definitions in DotNetNuke import/install.
Requesting Gravatar...
Hi Michael

You stated:
-------------------------
I desided not to implement it in my local DNN, but just split modules with multiple module definitions into separate modules.
-------------------------
Would you mind telling me how you went about this? I am considering doing this myself. I sort of understand the problem but can't see how to split up the modules.

By the way, in doing this do this do you have any issues upgrading to later versions?

Thanks

Alex

p.s. I logged another call in Gemeni you might be interested in:
http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=3708
Left by NukeAlexS on Jul 29, 2006 10:58 PM

# re: Support of multiple module definitions in DotNetNuke import/install.
Requesting Gravatar...
Ah forgot to say I'm running 4.3.3 now, are you? and are you still experiencing the same issue?

Cheers

Alex
Left by NukeAlexS on Jul 29, 2006 10:59 PM

# re: Support of multiple module definitions in DotNetNuke import/install.
Requesting Gravatar...
Alex,
I'm still on 4.0.3 version. I am not aware about any changes in 4.3.3 in this area.When To split modules with multiple module definitions into separate modules I've just created separate modules with single module definition in each, but in the same directory. It is standard approach in DNN, so I didn't have any problems. However I remember that attempt to delete one of modules that shares the DesktopModules subfolder with other modules can delete more than expected and break
other 'siblings'.
Left by Michael Freidgeim on Jul 31, 2006 7:59 AM

# re: Support of multiple module definitions in DotNetNuke import/install.

Your comment:
 (will show your gravatar)


Copyright © Michael Freidgeim | Powered by: GeeksWithBlogs.net