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
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Solution to AJAX toolkit problems (hover positioning etc.)Solution to AJAX toolkit problems (hover positioning etc.)
Previous
 
Next
New Post
11/6/2007 7:05 AM
 
Kindbergs.dk

Joined: 9/13/2007
Posts: 4

Hi!

After reading lots of and of treads here and on the ASP.NET site, I finallly found the answer in some obsure reply to somebodys question, and I am posting it here to be visible for all:

Ajax Toolkit controls such as AlwaysVisibleControlExtender and HoverMenuExtender only works in Internet Explorer 7.0 if the document has this identification:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

By default, this is NOT the document type of DotNetNuke 2.6.2, which has the result that those extensions only work in Mozilla Firefox.

To get it to work, simply open "/default.aspx" and add the above line after the "Register" tags. Then run DotNetNuke again and see that all your control extensions magically work in Internet Explorer too! (There is still some differences between the browsers in how they understand stylesheets and make margin/padding that you have to handle and test in both browsers, but that's apparently the way life is).

Maybe there is a setting somewhere in visual studio that also affects that line, and which can explain why it works for some people and not for others. If somebody knows, then let me know.

But my custom module which has a asp:DataList showing lots of records each with a HoverMenuExtender now all shops up the right place, instead of moving up by the same distance that the page scrolls down.

Hope this help other new module developers like myself.

 

Allan K.

www.kindbergs.dk - www.miniatureville.com
 
New Post
3/19/2008 9:52 PM
 
age

Joined: 7/29/2007
Posts: 5

Thank you for posting this.  This is the only way I've been able to use the AlwaysVisibleExtender however now other elements on my pages are rendering differently.

For example the height of my outermost table is set to 100% but it is not filling the page, and my text is now center aligned instead of left. 
 
New Post
3/20/2008 6:12 PM
 
Chuck Rizzio


Joined: 2/17/2006
Posts: 287

Alan, do you really mean DNN 2.6.2?  If, by chance you meant 4.6.2 there is an even easire way to accomplish this.  In your skins folder create a file and name it

"Your Skin Name".doctype.xml.  Example: "Horizontal Menu - Fixed Width.doctype.xml"

I believe this feature was introduced somewhere round version 4.5.x

In this file place the DOC TYPE declaration inside the following tag...

 

ASP.NET 
1
2
3
4
 
<SkinDocType>
<![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">]]>
</SkinDocType>
 

The skinning engine will see this file and use the DOC TYPE specified for all pages.  This is how we overcame the AJAX rendering problems.  Please note that this doctype causes some other problems with the way controls are rendered.  It appears that the default alignment of some (if not all controls) changes from left justified to centered.  This makes many of the standard modules look "funky".  For me, luckily the biggest impact is on "Admin" and "Host" screens which I can live with.  The other modules have issues but we have been able to get around most of them with style sheet changes.

Hope this is helpful to some.

Chuck R.
 
New Post
4/29/2008 8:46 AM
 
Marius Koen

Joined: 1/18/2007
Posts: 5

Hi Chuck

The popup now pops up, but as you said messes up all the other modules.

 

Any other suggestions? The modalpopup is really abit troublesome.

Thanks

Marius
 
New Post
9/25/2008 9:23 AM
 
Kindbergs.dk

Joined: 9/13/2007
Posts: 4

Hi Chuck and Marius.

I did mean DNN 4.6.2 - and now using 4.9.0 and got it working with the SkinDocType instead - much nicer fix :-)

And I am handling the centering bug using style sheets as I find the places where it happens. Firefox with firebug is excellent to pinpoint the style that need modifying.

As to how "Print" buttons and other stuff that open a popup window will ruin your page layout (because the code is injecting javascript before the doctype tag so browsers no longer recognises the doctype), you need to fix the bug in the DotNetNuke source code, in the file ActionBase.vb change this function:

        Private Sub DoAction(ByVal Command As ModuleAction)
            If Command.NewWindow Then
        ' old bad: Response.Write("<script>window.open('" & Command.Url & "','_blank')</script>")
        ' AKN change start
        Page.ClientScript.RegisterClientScriptBlock(Me.GetType(), "AKN_OpenWindow", "<script>window.open('" & Command.Url & "','_blank')</script>")
        ' AKN change end
            Else
                Response.Redirect(Command.Url, True)
            End If
        End Sub

("AKN" is my initials, I use it to track my core fixes to that I can compare new versions and copy the code until the bug will be officially fixed.)

I think similar fixes exist in the bug tracking system that are waiting for the core team to implement.

 

Best wishes

Allan K.
 
 Page 1 of 1
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Solution to AJAX toolkit problems (hover positioning etc.)Solution to AJAX toolkit problems (hover positioning etc.)


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