Forum

Hello there Lee or Joe:

I was wondering if you guys or anyone else knew how to create a module that would spread across a skin not the whole site though.  I know you can go to the settngs of a module and tell that module to duplicate on the whole site including all skins you may be using but I have a particular module that I want duplicated only across the skin in which it was first placed on since I have a particular pane created just for this particular module and if it distributes across the whole site I will go ahead and have to delete this module from skins that do not use this pane.

I have about 4 skins for different purposes and it would be a big time saver to be able to create the module once and have it auto place on all other pages with that skin but it would be a great time spender to have to go to all pages that use other skins which aren't designed to house this particular module (i.e. that as  a result would get dumped on the content pane) and delete them manually especailly this the site has 100's of pages.

I know you could place a skin object of sorts but I am not sure if that would work in this case.  Basically I need an iframe of about 300X315 placed in a contentpane designed to house this iframe.  I was doing it via the iframe module that comes with DNN but as I stated ticking the option for displaying module on all pages just isn't efficient in this case neither is it really efficient to manually place a copy of this iframe and its contents in every sub page that is desinged to house it but there are just enough other pages that aren't structured for this module to make it inefficient as well.

So I guess in long what I am trying to find is first is there a DNN solution using the framework to implement such a thing as a skinwide duplication of a given module instead of portal wide or host.

If this is not a feasible option how feasible is it to hard code an iframe with the correct src info, width, heighth, etc... into the table cell within the default.ascx file and use this instead.  Of course than again I guess you would be stuck with this hard coded bit of content in all pages within that skin so that even if their was say 2 or 3 pages you would rather not see it in there you could do nothing about it because it wouldn't be a module you could delete.

Well I am just brainstorming now as to how to go about this since my client would like this small window that gives a portal into other pages (within the same site) on pretty much every page that supports the skin it is made for.  It is to go on the home page and sub pages but pages with other skins it should not be placed on.

Thanks for any information you can give

Bo

• Issue 33 - Professional DotNetNuke Administration using SQL (Part 2)

• Issue 32 - Powerful Efficient Techniques for DotNetNuke Administration using SQL