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...Administration ...Administration ...Default.css has changed orderDefault.css has changed order
Previous
 
Next
New Post
11/2/2011 3:09 PM
 
I just installed 6.1 and found that default.css is now loading after the css in my skin. This is causing issues with default tags that don't have !important most specifically the a tag.
 
New Post
11/2/2011 3:29 PM
 
I think I am experiencing something similar. I had issues when migrating from 5.6.3 to 6.0.2 because I was actually excluding default.css before. Once I removed that a lot of my issues were resolved.

Now after upgrading from 6.0.2 to 6.1.0 I see some similar issues. Like the Manage button is displaying at the top left on many pages instead of actually hovering above the module instance.

Any good way to work around this would be very helpful.

Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
11/2/2011 3:45 PM
 
I have also found javascript order has been reversed as well. It's causing jquery errors. I have submitted a bug http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=18620&PROJID=2
 
New Post
11/2/2011 3:50 PM
 
Thanks for creating the ticket Robert. It took me about 3 weeks to iron out all the css, js, jquery issues on my site when moving to DNN 6.0.1 and I am hoping it won't take weeks to resolve this issue. I probably should have waited to do the upgrade but there was another issue introduced in DNN 6.0.1 that was being corrected in 6.1.0. So I wanted to do the upgrade ASAP. But if all else fails with this particular issue I do have a full set of backup files to do a restore until it is sorted out.

Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
11/3/2011 3:55 PM
 
I've detected just the same on my sites (I was crazy finding a solution). The inmediate solution is to change the dnn:STYLE controls by the dnn:DnnCssInclude control on the skin files.

Check here for the syntax:
http://www.dotnetnuke.com/Resources/Wiki/Page/Client-Resource-Management-API.aspx

I suppose that a fix for rendering the dnn:STYLE controls at the end for retro-compatibility is the solution for everybody, not changing the thousands of skins on the DNN ecosystem.

David Rodriguez
DNN Cloud Team Lead Engineer | Microsoft Azure MVP | Microsoft Azure Insider / Advisor

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Default.css has changed orderDefault.css has changed order


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