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, ...5.6.1 upgrade and CSS precedence5.6.1 upgrade and CSS precedence
Previous
 
Next
New Post
2/1/2011 3:51 AM
 
What I don't understand is that there is this in portal.css:

.CrossChildPageListLine { font-family:Arial, Helvetica, sans-serif; font-size:12px; font-weight:500; color:#585858; text-decoration:none; line-height: 1.2;} 
.CrossChildPageListLine A:link { font-style:normal; font-weight:500; color:#205E8E; font-family:Arial, Helvetica, sans-serif; font-size:12px; text-decoration:none; white-space: normal;} 

And the second definition seems to target the links, but the class is the class of the links themselves.
I think this should be:
A.CrossChildPageListLine:link

But it's unclear to me how that would have changed with the upgrade of DNN.

2 questions:
1. What is the most important attribute that changed? The color of the text?
2. Are you 100% sure that the default.css on the system before the upgrade was untouched?


@Lance, IMO default.css should be empty in the future :-)
 
New Post
2/1/2011 10:19 AM
 
Thanks for your attention, gents.  I've changed the selector to a.CrossChildPageLIstLIne:link (and :visited, :hover, :active) and am seeing *some* control over the CSS now.  However, I am unable to use a reverse indent with any effect.  I am using: 

          text-indent:-50px;
          padding-left:20px;

But it is as if the text-indent portion is not working in the two browsers I use for testing (IE8 and Firefox).  Firebug shows that the browser is receivng the text-indent, but it has no effect.

This worked great until the upgrade.

To your questions:
1. Important attributes: no text decoration, reverse indent
2. The site was upgraded by my host (PowerDNN). They're normally pretty good about not touching stuff.  Having said that, the default.css has the date of the upgrade and is smaller in size than the default.css file from before the upgrade.  Should I restore an old version of the default.css?
 
New Post
2/1/2011 11:09 AM
 
There were some moves recently to streamline default.css and portal.css - to improve performance. If you are having particular problems - I would have a look at the differences between your version of default.css and the new one - and then add any differences into your skin.css file. That way as the default.css and portal.css files gets updated over time - your site wont be effected by any other changes. Westa
 
New Post
2/4/2011 11:46 AM
 
Paul Martin wrote:
1. Important attributes: no text decoration, reverse indent
2. The site was upgraded by my host (PowerDNN). They're normally pretty good about not touching stuff.  Having said that, the default.css has the date of the upgrade and is smaller in size than the default.css file from before the upgrade.  Should I restore an old version of the default.css?

1) You would have better, more reliable results from using margins on the whole list.
2) That sounds about right.  I would not restore the old version as you will just have this problem on the next upgrade. Better to do as you have and amend the skin files.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...5.6.1 upgrade and CSS precedence5.6.1 upgrade and CSS precedence


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