Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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, ...Module Actions problem with DNN 6Module Actions problem with DNN 6
Previous
 
Next
New Post
9/19/2011 11:36 AM
 
Phil Biggs


www.chord9.co.uk
Joined: 1/31/2006
Posts: 170
Hi,

I'm trying to get a v5 compatible custom skin working with v6 and have found a problem which I will attempt to describe. When I create a skin pack, I usually need to provide a range of containers for different purposes. It's usually necessary to define individual styles for each container, so for each container I'll create a <containername>.css along with each <containername>.ascx. In this way <containername>.css can override any preceding styles.

With v6, the 'actions' function is provided by  an instance of DDRMenu that seems to be inserted at the point  that ContentPane is instanced e.g.

<div class="mystyle">
<div class="content" runat="server" id="ContentPane" />
</div>

The initial appearance of the ModuleActions pop-up is defined in the default.css, but  when 'mystyle' is defined in <containername>.css (or even container.css), any elements  in common e.g. ul, li, a, img etc get overridden. This causes the appearance of ModuleAction pop-up to change from that defined in default.css. This change is not necessariily for the best either.

It's possible to work around this by including all of the ModuleActions styles from default.css in each <containername>.css preceded with 'mystyle' - but, this would create a significant amount of extra work and maintenance overhead.

This seems to be a failry fundamental problem to me... or am I missing a trick?

How can the ModuleActions pop-up styles be isolated from re-definition in lower level stylesheets?

Well, I've tried to explain that clearly!....hopefully someone can either put me on the right track or recognise this as a serious problem when it comes to the skinning process.

Rgds

Phil
 
New Post
9/21/2011 1:33 PM
 
Phil Biggs


www.chord9.co.uk
Joined: 1/31/2006
Posts: 170
....well perhaps I didn't describe the problem clearly. However after a couple more hours of ceaseless toil, I finally got on top of this. If you find (in v6) that the ModuleActions pop-up is inheriting styles from your container (detrimentally) then the thing to do is ensure that all you text area container styles are preceded with '.Normal'. So if your container looks like this:

<div class="mystyle">
<div id="ContentPane" class="content" runat="server">
</div>

then style defs should look like this:

.mystyle .Normal a {color: #94be2e; font-weight: bold;}
etc

It may well be that this has always been the best way to define container styles, however with v6 being full of pop-ups and jquery stuff it would seem to be more important now.

Be interesting to see how many 3rd party skins behave themselves in v6.
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Module Actions problem with DNN 6Module Actions problem with DNN 6


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