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, ...Using @importUsing @import
Previous
 
Next
New Post
4/4/2008 3:39 PM
 

John Valentine wrote: The only answer I have been able to come up with is to edit the default.css file and keep a change file that I need to merge every time I upgrade. It isn't the best solution, but its a good work around until the DNN dev team can correct this oversite and once again begin adhering to the standard.

Hi John,

it seems to be a good timing for your post, because some volunteers (including myself) formed a new Events team some weeks ago, and although our main goal is to get a debugged DNN 4 / ASP.NET 2.0 version out of the door, we are planning (as a second step) to implement feature requests and enhancements; see post "Any reproducable bugs and/or suggestions for enhancements?" . Perhaps you'd like contribute your suggestions or even help us to create standard conform themes? You're welcome!

 
New Post
4/4/2008 6:27 PM
 

I agree you could wonder why a developer would use !important in modules CSS in external files or inline.

My initial post was about the actual problem, not the concept.

BTW, there is no !important in DNNs "default" default.css afaik.

If the module load a CSS file and it's loaded before skin.css (it should) then you can overwrite any value that's defined with !important by using !important in skin.css.

If that doesn't work either, please post a link to an example...

 
New Post
4/15/2008 12:05 PM
 

Hey Timo,

For my part, I understand what your original post was saying, and I hope you didn't think that my comment was directed at you personally. I was simply explaining that the problem bumps into the conceptual impliementation of CSS in the modules framework.

My copy of DNN Events has "!important" sprinkled throuought the stylesheet same as Dawn's. Unfortunately, I don't know which CSS class you are referencing. I am speaking of the "DesktopModules\Events\Themes\Default\default.css" file. I have traced the use of !important back several releases (even as far back as DNN433 Source version). It is plainly obvious that the developers were not adhering to the standards. The source version stylesheet is called module.css and is distributed in Events 3.2 and later as default.css in the path referenced above.

 BTW, I have posted this as a minor bug in gemeni.

Thanks again.


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Using @importUsing @import


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