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

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Sitewide management of skin/containersSitewide management of skin/containers
Previous
 
Next
New Post
4/23/2013 9:03 AM
 
Stuart,

This sounds like a wrong approach (for DNN) to me. I think that skin objects are the way to go if you have stuff that should appear on every page. Skin objects are every bit as programmable as modules, but they are more technical and lack any pretty UI to control them.

So somthing like a page footer, for example, I think belongs in the skin, not in a module instance that you then try to push onto every page or most pages.

A module instance is NOT somthing assigned to a page. In DNN it's at the intersection of a page, and a skin pane, that's a lower level of granularity than the page. This gives DNN arguably more flexibility than some of the competition, but does mean that the concepts cannot be trivially interchanged between the different CMS's. In DNN it may, and often is, repeated at that intersection (two HTML modules in the same pane for example).

There is one blunt instrument available here. You can have the same module instance placed on EVERY page. I have experimented with that setting in the past, and largely abandoned it.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
4/23/2013 9:13 AM
 

Stuart,

  I think that is a great suggestion to allow modules to be "copied" to select pages quickly and easily without being an all or nothing proposition.  If you write it up as a Community Voice suggestion then we can see if the community votes it up.


Joe Brinkman
DNN Corp.
 
New Post
4/23/2013 9:20 AM
 

I agree, that looks by far the best approach. some questions.
We would probaly have to convert / develop our existing plugins anyway but what about some of the commercial modules that we might be using, are we able to use them as Skin objects?.
For example if they are in the desktop modules folder can we not just reference them as we would the menu object etc, I guess the set up options might be difficult to implement?.

Second question, is there any good documentation on developing skin objects out there as it does look as though we should develop our own skin objects.

 
New Post
4/23/2013 9:42 AM
 
Joe Brinkman wrote:

Stuart,

  I think that is a great suggestion to allow modules to be "copied" to select pages quickly and easily without being an all or nothing proposition.  If you write it up as a Community Voice suggestion then we can see if the community votes it up.

 Done.

 
New Post
4/23/2013 10:51 AM
 
stuartf wrote:
[...]

Second question, is there any good documentation on developing skin objects out there as it does look as though we should develop our own skin objects.

 Stuart,

there is a blog by Mitchel Sellers treating this, and some more results if you use Google. Another way (that I often use) is taking a simple skin object and see how it's done by reading the source code. Most of the development is not too difficult if you have some experience with ASP.Net web forms.

Best wishes
Michael


Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Sitewide management of skin/containersSitewide management of skin/containers


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