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

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Customized module style - how to share images between multiple portalsCustomized module style - how to share images between multiple portals
Previous
 
Next
New Post
11/1/2009 7:57 PM
 

Hello all,

I am in the process of customising the style of a Module for multiple portals; some Portals will use the same set of images for assets such as buttons/background images etc and other Portals will require a different set of images. I have started by overwriting the styles defined in the Module.css within each Portal's Portal.css file.

Initially, I have placed the image assets required for the Module in each Portals Assets directory; however, this means that there are a lot of redundant images for all portals that use the same set of images. I was wondering how other people have shared these images between Portals?

My initial idea was to simply create a SharedAssets folder within the Website/Portals directory and reference the Portal.css to these images to reduce redundancy. Does anyone have any other/better suggestions on how to achieve this?

Thanks for your time, much apprecaited.

 
New Post
11/1/2009 9:05 PM
 

George wrote

My initial idea was to simply create a SharedAssets folder within the Website/Portals directory

Correction: The directory I created the SharedAssets folder was the Website/Portals/_default directory (as this is where shared resources such as skins are stored so it seemed like a logical place).

George

 
New Post
11/1/2009 10:42 PM
 

Before you get yourself caught in a real mess, I have to ask three questions.

Q1) How many images are you concerned about?
Q2) What is the total size of the images involved?
Q3) Why would you need only some portals to use the same set of images?

It would be extremely difficult to re-architect the functionality of DNN for a few odd portals. There is so much going on internally to manage the portal folder structure that your module will probably end up breaking something else. Thankfully you can use skins to manage the overall look of your portals and reuse them as required.

There is nothing wrong with copying your folder structure from one folder to another and if the portals are very similar you can use the built in security to manage who sees what from a single portal.

Unless I am missing some fundamental issues, you should concentrate on the business case first.

Disk space is cheap; reverse engineering will cost far more time and money.

I hope this is of some help to you.


Dwayne J. Baldwin
 
New Post
11/1/2009 11:01 PM
 

Dwayne, thanks for your reply.

1. For each module there are approximately 10-20 images and there are approximately 50 modules (this will most likely grow over time).

2. The size of the images are generally very small ~ 10kb or less (things like buttons, shadows, etc), so storage is not an issue as you suggested.

3. There are 4 different 'brands' which require their own styling and separate set of customized module images. For each 'brand' there may be up to 100 Portals, and this is why I thought I would create a SharedAssets folder with 4 sub folders (one for each brand) rather than to copy redundant module images accross up to 400 Portals. It's not so much a size issue; moreso a maintenence issue. Also, this ensures that content managed assets are not mixed with module assets.

I was thinking that if each Portal's portal.css was customised to point to this shared folder, then this would be much easier to maintain and reduce redundancy of these assets. Would having this extra folder in the Portals/_default directory disturb the architecture of DNN? Would it be better to store it independent of the DNN folders and perhaps point to it via a virtual directory?

Thanks,

George

 
New Post
11/2/2009 4:30 AM
Accepted Answer 

you may create any folders in /portals/_default, you like. Superusers ("host") may access it via File manager in Host menu.

you might also consider "abusing" an unused portal setting for a value you may use as an directory id to specify the image directory, when combining the path dynamically. 


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Customized module style - how to share images between multiple portalsCustomized module style - how to share images between multiple portals


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