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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0AJAX - Nesting Update PanelsAJAX - Nesting Update Panels
Previous
 
Next
New Post
4/26/2007 3:07 PM
 

I would like to have multiple areas of my module updated independently.  I have been able to accomplish this by adding my own Update Panels to my control, but it only works if I UNCHECK the "Supports Partial Rendering" option in the Module Definition.  This seems counter intuitive.  I believe that the problem is that with partial rendering enabled, the entire module is wrapped in an update panel, effectively nesting my manually added panels.  I found a tutorial that explains that for the nested panels to work as expected, they need to have UpdateMode set to "Conditional" (http://ajax.asp.net/docs/tutorials/CreatingPageUpdatePanel.aspx).

Is there any option or recommended solution to set the framework's generated update panel to Conditional Update Mode?

Thanks!

 
New Post
4/27/2007 7:32 PM
 

Hello,

I'm a little confused by your post and I'm trying to do a similar thing. It seems like you have it working the way you want. From my understanding (I'm just getting started with AJAX), using the "supports partial rendering" option is the quick and dirty way of getting AJAX-like functionality without any AJAX coding. If you've already gone and added nested panels, with presumably more complicated update triggers and such, why would you want the framework to generate an update panel? (I'm not trying to criticize you, I'm just trying to understand what *I* need to do to do the same thing).

I'm still unsure of what I need to do to use my own update panels instead of the framework generated panels. Do I have to register with the Script Manager? In the Page Load event?

Tom

 
New Post
4/27/2007 11:50 PM
 

Please always search before posting. I've blogged about this here: http://nes.nesinteractivos.com/Weblog/tabid/537/EntryID/63/Default.aspx


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
4/30/2007 4:13 PM
 

I did search.  In fact, the link you reference is the first thing I looked at and is where part of my test code came from.  I've been to all of the links in your very helpful "Getting Started" post at (http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/125515/scope/posts/Default.aspx). 

I started seeing odd behavior when I started combining concepts from several of those posts.

Maybe I'm just confused by the initial blog entry; you say "Select de checkbox for Supports Partial Rendering ", but the screen capture shows the box unchecked.  I went with the text and checked the box; this seems like the logical setting to use with a module that you expect to support AJAX.  Was I supposed to go with the image instead and leave the box unchecked? 

It seems like when you manually add your own Update Panel, you need to leave Supports Partial Rendering unchecked in order to get the expected behavior.

Here's another reference to using multiple or nested panels outside of DNN.  These combinations will not work in DNN when Supports Partial Rendering is checked.  http://ajax.asp.net/docs/tutorials/CreatingPageUpdatePanel.aspx

Thanks for your helpful blog entries and especailly for the forum post with the AJAX + DNN Resources.  That is a great starting point!

Thanks,
Glenn

 
New Post
4/30/2007 4:48 PM
 

Hi,
I'm just getting started as well.  Start with this Forum post: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/125515/scope/posts/Default.aspx

It has several samples of varying complexity.  I started with the AJAX Sample application in "Creating a DotNetNuke Module using ASP.Net AJAX" by Michael Washington (Third link from the page above).  Then I incorporated the sample code from the first two links onto the same control.  This gave me several update panels that I expected to update independently.  What I found was that any time one panel updated, ALL OF THEM updated.  I finally figured out that it was due to the framework generated UpdatePanel that is being created when "Supports Partial Rendering" is checked.  Here's the reference that explains that: http://ajax.asp.net/docs/tutorials/CreatingPageUpdatePanel.aspx . 

The solution is to uncheck Partial Rendering and register your own script manager in Page_Load.  Easy enough, but this seems like a work around.  It would be nice if there were some additional configuration options in the module definition, like the abiltiy to specify Conditional Updates.

I haven't tried this yet, but I suspect there is going to be a similar issue on pages where multiple modules set to "Supports Partial Rendering" have been added.

Add something like this to Page_Load to register your own Script Manager:

 

             If DotNetNuke.Framework.AJAX.IsInstalled Then
                DotNetNuke.Framework.AJAX.RegisterScriptManager()
                Label2.Text = "AJAX Is Installed"
            Else
                Label2.Text = "AJAX Is not installed"
            End If

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0AJAX - Nesting Update PanelsAJAX - Nesting Update Panels


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