Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Use Existing Module -- Settings not copiedUse Existing Module -- Settings not copied
Previous
 
Next
New Post
1/23/2007 11:13 AM
 

I'm developing a custom Menu builder control and want to be able to add it to one page, then copy it to new pages from there on out.  It references the Module ID appropriately, but the settings do not copy (which is a problem because the menu knows if it needs to render as a "menu" or as a "treeview").  I have default settings to render it as a tree with no formatting, but again, if I've already set all the parameters in the base page, i'd really like if it copied everything.

Any ideas what i'm missing (ie, some function or interface I need to implement to copy the settings?).

-- Fooberichu


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
1/23/2007 11:51 AM
 

There are two types of settings,  ModuleSettings and TabModuleSettings.

The first ModuleSettings apply to all instances of a Module, the second only applies to the current instance.

So, in order to get the settings the same in each instance you need to create the setting as a ModuleSetting.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
1/23/2007 11:57 AM
 

Sorry, I apologize... let me clarify my intentions.  I actually knew about those two different settings, but here is what I'm thinking of and maybe what I want isn't possible:

I want to initially create the menu with settings (I am using TabModuleSettings, not Settings), but then I *may* actually want them to look differently, maybe not.  I know it sounds weird, but maybe on one page with that menu structure, I want it to be a treeview with styles x,y,z; then on another page, I want it to show up with the exact same items, but use a horizontal menu with styles mx, my, mz.  On that note, I want to be able to add/edit/delete items and have it affect all pages associated with this module without affecting the individual styles that I may have overridden on other pages.

Does that make sense?  Maybe I'm thinking too far out of the box and going against the grain on this one.

Thanks for your quick response though.

-- Fooberichu


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
1/28/2007 1:30 PM
 

Thinking back to the ModuleSettings vs TabModuleSettings... it makes perfect sense to do it using ModuleSettings and not TabModuleSettings.  I think I was just overthinking the problem and didn't realize how stupid that sounded.  I'm switching it to straight ModuleSettings now.

-- Fooberichu


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Use Existing Module -- Settings not copiedUse Existing Module -- Settings not copied


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out