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.0ModalPopupExtender is BROKEModalPopupExtender is BROKE
Previous
 
Next
New Post
9/27/2007 8:20 AM
 
Jon Paskett

Joined: 4/27/2003
Posts: 202

Has ANYONE successfully implemented the ModalPopupExtender WITHOUT modification and recompiling of the AjaxControlToolkit OR Adding the SkinName.DocType.xml file? Either is unacceptable in my opinion. Creating the XML file allows the ModalPopupExtender to work correctly at the cost of all controls being centered on a page.

What is going to be the permanent solution to this? CSS? AjaxControlToolkit modification? Is there a plan to identify and isolate this problem in DNN? Has anyone made a modification to the AjaxControlToolkit code to fix this and has the change request been submitted to AjaxControlToolkit team?

Any help here would be appreciated. I have several uses I would like to implement this functionality but cannot.

Jon
 
New Post
9/27/2007 8:54 AM
 
Matthew Doyle

Joined: 3/8/2007
Posts: 32

I think its quite simply that DNN is rendered in quirks mode without the xml files and the toolkit requires HTML standards compliance. 

Since quirks mode renders pages differently than standards compliance mode, you will have to edit the skins in order to reflect the standards compliance mode in order to get this to work. 

I think the AjaxControlToolkit team made a hard requirement not to support quirks mode.  I gather that the effort to convert the whole web site to standards compliance mode would be a time-consuming task, so I propose tying to find some other way to get this functionality to work.

I have looked into JQuery (and the related BlockUI addon for the modalpopup functionality), but I cannot get it to work with DNN/AJAX.NET.

 
 
New Post
9/27/2007 11:08 AM
 
Jon Paskett

Joined: 4/27/2003
Posts: 202

With other posts in the forum it seems that Quirks Mode compatibility is the requirement/culprit. The question now is identifying the most logical place to make the corrections. Can the AjaxControlToolkit be modified with minimal effort and repercussions to the rest of the toolkit? The modifications required to get DNN compatible seem to be extensive. I'm not qualified to say who's responsibility it is to fix this issue (DNN or AjaxControlToolkit developers) but I DO know the TWO TEAMS need to collaborate in order for everyone to take advantage of these functionalities. I think it would be nice to know if a dialogue has been initiated between the two. Have you heard anything?

Jon
 
New Post
9/27/2007 11:54 AM
 
Brian Dukes


Brian Dukes's Avatar

Brian Dukes's Avatar

www.engagesoftware.com
Joined: 8/25/2006
Posts: 896

As was said, the culprit is rendering in Quirks mode.  As DNN allows you to render as XHTML, I don't think either the AjaxControlToolkit or DNN is responsible, they have given you a solution.  It seems that the culprit in your situation is your skin that is relying on quirks mode to render correctly.  That is the place where your efforts would be best placed to get everything working smoothly.  If that isn't an option, you're going to need to make some other compromise will need to be made, probably in recompiling the toolkit.  If all that is happening to your skin in when rendered in XHTML is that modules are rendering with center alignment, I would think that you could probably alter your skin just a little and find a way to force it to align left.  That, from what I see, sounds like the easiest solution by far.

Hope it helps,

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
9/28/2007 7:57 AM
 
Jon Paskett

Joined: 4/27/2003
Posts: 202

dukesb11 wrote

As was said, the culprit is rendering in Quirks mode.  As DNN allows you to render as XHTML, I don't think either the AjaxControlToolkit or DNN is responsible, they have given you a solution.  It seems that the culprit in your situation is your skin that is relying on quirks mode to render correctly. 

Sorry but I have to totally disagree with you on parts of this statement dukesb11. Regardless of where the final solution lies the fact is this; I must modify EVERY skin in my web site or never use this technology. Even the default DNN skins have to be modified. I have two choices; NOT use the emerging AJAX technology in DNN (this functionality anyway) or re-engineer EVERY skin on my site. Being realistic I feel this is totally unacceptable. I will now ask; "Why does DNN render in Quirks Mode? Can it be easily changed? In which platform should this problem be fixed? What is the difficulty level?"  NOBODY's to blame here but as technology advances we're force into compliance. The solution identifed thus far is a bandaid; I'm looking at a bigger picture.

Jon
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0ModalPopupExtender is BROKEModalPopupExtender is BROKE


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