Update Panel hates me
Okay, here is an error that I manage to get occasionally, no real pattern that I can notice.I don't have any filters, Response.Write(), HttpModules or trace enabled. (At least, none that writes to the outgoing string). The issue is that sometimes, the return result of an Update Panel postback would return the whole page, instead of just the parts inside an update panel. It is as if it decides to simply ignore the update panel, and just go its merry way onward.
Anyone has run into this before?
Comments
This is a known issue with ASP.NET ajax . You can turn EventValidation='false' (they actually propose that as a solution...) .
Here's one post that has details...
http://weblogs.asp.net/leftslipper/archive/2007/02/26/sys-webforms-pagerequestmanagerparsererrorexception-what-it-is-and-how-to-avoid-it.aspx
We had the same thing and corrected it the same way last week. It's one of those pet hates out there...
Mike,
I have enableEventValidation="false" at the web.config level, so I don't think that this is the issue.
At any rate, it looks like something cause the UpdatePanel to send the whole page, no just the parts under the update panel.
Have you tried enabling Fiddler so you can go back and see what might have been different with the requests that resulted in full page HTML being returned?
ATLAS is also very finicky with invalid html and will revert to a full postback when the xhtml is invalid. Are you sure that you don't have periodic xhtml validation errors?
Yeah, I get this now and then too...I tried enabling the Fiddler but then I couldn't replicate. Kinda hard to debug. Only thing I noticed that after adding AjaxControlToolkit control on the page, I'm seeing this more often. I could be wrong though!
I've got one with Forms Authentication. when user log out on one page but there is 2nd open and he perform some action on 2nd page's update panel
I've got one with Forms Authentication. when user log out on one page but there is 2nd open and he perform some action on 2nd page's update panel
That is possible, except that I get the page that I would expect, not the login page.