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.0Manage exceptions when Partial Rendering is enabledManage exceptions when Partial Rendering is enabled
Previous
 
Next
New Post
10/17/2008 9:37 AM
 

Hello everybody,

I'm in the process of enhancing our portal to use the ajax capabitilies of DotNetNuke. So far, the process has been going on smoothly, mainly consisting of adjustments in my user controls to accomodate for the special uses of the ScriptManager.

However, i've been encountering the following problem; previously, when an exception is raised in my module, i usually redirected the user on a page providing debug information (when the user is a developper) or on a page providing feedback to the user (something along the lines of "we're aware an error popped up, we've logged it and it's going to be processed to avoid its reproduction")

But since Ajax doesn't care about these redirections, what's happening is that the Ajax Framework returns the whole html webpage and tries to parse it. What i would like to do is to be able to either redirect the whole page through Ajax; another option could be to popup the error message in a modalbox, but i would like it to be as smooth as possible. What i mean by that is that i would like not to change too many things. In both cases, another question arises: is there a way to add a handler on server side errors when using the Ajax mode of DotNetNuke.

Thank you for reading, and don't hesitate to ask for more details; i'm really stumped by a lack of details here...

Samy

 

 
New Post
10/20/2008 8:13 AM
 

Hello again,

since friday, i've been doing some tests regarding this problem. I'm using a custom Error handler for the DotNetNuke website we're using (because i need to change behavior between the development and the production environment), which means that the "Use Custom Errors" flag of the host configuration is not set in DNN

Apparently, what the system doesn't like is that it is a whole new page written entirely for debugging purposes. Here the error message that is given:

Sys.Webforms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.

Details: Error parsing near '

<!DOCTYPE html P'.

I tried to set the Custom Errors flag of DotNetNuke to true, but the system just gave me a weird page, only rendering the skin and no inner modules.

Do someone have ideas, or even examples of how they handled it? Is there a way to specify our own handlers to the auto-inserted UpdatePanel? How can i keep the previous behavior in a way that won't blow up when an error happens? Is it even possible?

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Manage exceptions when Partial Rendering is enabledManage exceptions when Partial Rendering is enabled


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