Saturday, July 31, 2010
  Search
 
Register
Login
 
Creating new DotNetNuke HTTP Alias Records
 Setting up DotNetNuke to handle serving requests for Portal Alias records is a breeze. You can use these records to direct your site to handle requests for multiple domain names to one website with ...

Find this article and more in the category

Read This Article . . .

Upgrading to DotNetNuke Cambrian 5.0 from DotNeNuke 4.x
If you're looking to try out the new DNN Cambrian package, you can upgrade previous DotNetNuke installations with the following steps. Remember, as of right now, the DNN 5.0 Cambrian package availabl...

Find this article and more in the category

Read This Article . . .

DotNetNuke 5 Cambrian Extropy Skin Features and Limitations
The new DotNetNuke Extropy skin looks very cool from a distance...leaps and bounds above the old default blue skin. But, it's got some limitations you should know about upfront.

Find this article and more in the category

Read This Article . . .

Using DNN to take Advantage of GoDaddy Domain Names
Let's face it, GoDaddy is cheap. Pay for the hosting services and the domain names are $1.99, not a bad deal. And even without hosting services, you can pick up domain names for as low as $6.99. Put ...

Find this article and more in the category

Read This Article . . .

Setting Up Multiple Websites
You can create multiple distinct, (mainly) independent websites with one instance of a DNN installation on your web account. In lamens terms, this means that you can purchase ONE web hosting accoun...

Find this article and more in the category

Read This Article . . .

How to Utilize AjaxToolKit with DotNetNuke Portals
Integrating the AjaxToolkit into DotNetNuke modules is super easy. But, can be frustrating if you're not sure how. Find out how to Ajax enable your modules in less than 5 minutes now!   The ...

Find this article and more in the Module Development category

Read This Article . . .

More Ways to Install DotNetNuke Modules with the URL Method
While DotNetNuke has a built in mechanism for installing modules, there is another method you can use as well. This is a great alternative to use especially when you are trying to install larger mod...

Find this article and more in the category

Read This Article . . .

Installing Active Directory Authentication Package on DotNetNuke
DotNetNuke has abstracted the authentication providers away from the core giving site owners the ability to add new authentication systems. You can see in the picture below that by default, the DotNe...

Find this article and more in the category

Read This Article . . .

Installing DotNetNuke on the root of GoDaddy - 8 Simple Steps
If you have are having a hard time getting DotNetNuke installed on the root of your hosting account, read this article to find out how. This article was originally written for a the specific purpose ...

Find this article and more in the Hosting Provider category

Read This Article . . .

SERIES: Anatomy of a DNN Web.Config File-connectionStrings
The section holds all the necessary information for database communication from your website. At minimum, there will be at least one connection string for any DotNetNuke website...

Find this article and more in the category

Read This Article . . .

Recently Added Articles

Minimize
Article List

 

Fixing IE's Hover Problems in DNN

2/27/2009 1:28:33 PM - By Briana Tarrance

Category: | | Comments 0

 

 

Related Links

Fixing :hover Styling

So you have designed a great skin, skin object or module for DNN and it uses the :hover attribute and looks fantastic in Firefox. Now, you find out that nothing works in IE because IE doesn't support the :hover attribute on the elements you've used.

You can fix the issue pretty quickly with the help of a small .htc file available for free download. But, to get it to work in DNN you just have to make sure you place it in the proper place.

Download the following files:

Hover Fix:  Whatever:hover

Place the downloaded file in the ROOT directory of your DNN setup.

Then add the following to the DEFAULT.CSS file.

/* background color for the content part of the pages */
Body
{
    behavior: url(http://localhost/dnn5/csshover3.htc);
    background-color: white;
    margin: 0px;
}

* where http://localhost/dnn5 is the full path to the root of your DotNetNuke installation

The reason for this is that the location of the .htc file is relative to the .html file...not the skin or the CSS stylesheet. Due to the dynamic nature of DNN and all the pages being generated off of the Default.aspx page, the file must be placed in the root of your website and linked from there.

The reason you  have to use the full path is because the Default.css file is located in the Portals/_default folder. I tried using other methods to traverse the path without requiring the full path to be hard coded, but I wasn't able to get it to work that way. If anyone else finds a way to make this happen without requiring hard coding, I'd love to hear it.

I also tried using this from the Portal.css as well as the skin.css, again, with no luck. All other solutions are appreciated.

 

image image IE Hover Fixed in IE6 and DNN
FireFox Displaying Properly IE7 Displaying Properly IE6 Displaying Properly
powered by metaPost

 

 

 


 
 
Copyright 2008 by Virtual-Essentials.com Privacy Statement    Terms Of Use