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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Enabling AJAX - Repository ProblemsEnabling AJAX - Repository Problems
Previous
 
Next
New Post
5/13/2007 9:22 PM
 

I have a clean install of version 4.5.1 running on an XP Pro IIS 6 machine and have enabled AJAX on a page with the repository and links modules on it.  I have edited the proper user control for both modules to "supports partial rendering" but only the links module seems to work without error.  The repository module throws different browser errors according to if the user is trying to download a file or visit an external url. Only the detail section of the error message changes. I switch between the default repository skin (downloads)  and directory skin(visit)  but have made no modifications to them.  I also have the default dnn blue skin on my site.  If I go back an uncheck "supports partial rendering" for the repository module, everything works fine.  Here are the errors for both types of actions perfomed by the user:

VISIT - Go to external url - 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 '<script> window.open('.

DOWNLOAD - 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 'JFIF'.

Any insight appreciated.

Paul

 
New Post
5/13/2007 9:40 PM
 

It's a known issue in the AJAX implementation in DNN 4.5.1.  It will be fixed in the DNN 4.5.2 release

 
New Post
5/14/2007 10:38 AM
 

Steve,

Any chance you can elaborate on the "Known issues" with AJAX in 4.5.1?


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
5/14/2007 2:27 PM
 

I apologize for speaking so quickly before. I checked with Shaun so that I could fully understand the problem and it appears that simply upgrading to 4.5.2 when it's available will *not* solve the Repository issue. There are 2 ways to enable AJAX support for a module, letting the core framework do it, or build it into the module itself. When the core framework does it, it cannot know much at all about each individual module, so it does the best it can, it wraps the entire module in an AJAX UpdatePanel. There is a known limitation with streaming content from within an UpdatePanel. You can search on the ASP.NET AJAX forums for more information. Since the Repository module uses a streaming method for both uploading and download, allowing the core to wrap the entire module in an UpdatePanel results in the problem you are seeing.

The 4.5.2 release will include some changes to the core AJAX framework to provide module developers more granular control over which *parts* of their module should be wrapped in an UpdatePanel and which should not. Additionally, there will be changes to the URLControl which uses the same core streaming functions to upload/download content as the Repository Module does. However, this requires code changes in the module itself.

So, the current Repository version 3.01.10 cannot support AJAX by simply checking the 'supports partial rendering' option.

Also, I've already submitted a new release of the Repository module to the Release Process, so the upcoming version of the Repository module, 3.01.12 will also *not* support AJAX by simply checking the 'supports partial rendering' option.

Finally, once 4.5.2 is close to being ready, and as soon as I can understand the code changes I need to make, I will submit a 3.01.13 version of the Repository to the Release Process that *will* include built-in AJAX support.

Sorry for the confusion earlier, I didn't fully understand the issue, but that didn't stop me from replying :)  Hopefully this will make this clearer regarding AJAX support in the Repository module.

 
New Post
5/14/2007 2:48 PM
 

Steve,

I greatly appreciate the detailed response, that all makes sense with the AJAX implementation, and actually I know know the reason why my other testings with specific modules have falied when enabling AJAX.  (The URL control was the cause.)

 


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Enabling AJAX - Repository ProblemsEnabling AJAX - Repository Problems


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