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 PUBL'.
I think its somethihng to do with how Master Pages is implemented in Umbraco v4 that is causing this. Any ideas as to why this may have happened, and what i can look at to try to solve it?
i'm doing any Response.write or Response.Redirect in the updatePanel I'm not using any response filters I've disabled server trace I'm not using response.transfer
But, regardless of the above, this works fine using the same usercontrol on an Umbraco v3 site, which leads me to believe its somethign to do with v4 that's caused this.</p>
</span>
I've been offline for a few days.. gonna pick this one up again today. Think i'll do some diff's between the v3 and v4 outputted HTML and see if that gives me any clues... any other troubleshooting tips?
So when i'm trying to refer to elements from my code, its all falling apart cos the naming conventions are all out of whack... has anybody found an elegant way to work around this issue?
Dammit, that's not the problem. FindControl("..") works fine and successfully returns the clientID of the control being requested, so there's no issue there.
Again, I have no idea what it is. if anybody wants to throw in their 2c worth, i'd really appreciate it (no matter how small or silly it may sound - it might help)
PageRequestManagerParserErrorException - Only since upgrade to v4
I have a custom user control that i use in a page... since upgrading to version 4, it seems this user control wont work any longer.
The user control contains an ajax uploader control (support request post here: http://cutesoft.net/forums/53732/ShowThread.aspx#53732</span></span>
I think its somethihng to do with how Master Pages is implemented in Umbraco v4 that is causing this. Any ideas as to why this may have happened, and what i can look at to try to solve it?
FYI, here's a blog post that describes the error and its possible causes:
http://weblogs.asp.net/leftslipper/archive/2007/02/26/sys-webforms-pagerequestmanagerparsererrorexception-what-it-is-and-how-to-avoid-it.aspx
i'm doing any Response.write or Response.Redirect in the updatePanel
I'm not using any response filters
I've disabled server trace
I'm not using response.transfer
But, regardless of the above, this works fine using the same usercontrol on an Umbraco v3 site, which leads me to believe its somethign to do with v4 that's caused this.</p> </span>
hmmm... no ideas?
I've been offline for a few days.. gonna pick this one up again today. Think i'll do some diff's between the v3 and v4 outputted HTML and see if that gives me any clues... any other troubleshooting tips?
Okay, i think i've located the problem. It seems v4 prefixes all html element IDs with something like this:
So when i'm trying to refer to elements from my code, its all falling apart cos the naming conventions are all out of whack... has anybody found an elegant way to work around this issue?
Dammit, that's not the problem. FindControl("..") works fine and successfully returns the clientID of the control being requested, so there's no issue there.
Again, I have no idea what it is. if anybody wants to throw in their 2c worth, i'd really appreciate it (no matter how small or silly it may sound - it might help)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.