I'm facing this issue for a while, still can't find a rational solution to that, I'm hoping for some external advice here.
I have a pretty complex ascx control in a page. In this user control I have an update panel as a container of a TabContainer. I have a number of tabs on it, each of them hosting a GridView with many controls.
I have used toolkit release from september 2009 (30930) for a long time on this page, and all was running pretty fine till then.
When I tried to update AjaxControlToolkit to the latest release (may 2012) I started to face a really annoying issue: whenever I try to fire a GridView command on the first tab page freezes and I get error in subject. More precisely:
Sys.WebForms.PageRequestManagerServerErrorException: Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
Please note the following:
1. The error is showed just for command events, I can still fire sorting commands on the gridview, and I can interact with the whole page without any other issue.
2. On any tab other than the first all works: commands are fired and executed just fine. Each time I return on first tab the issue shows up again, there's no difference between first load and following postbacks. GridViews inside tabs are engineered exactly in the same way and what's changing between them is just the datasource.
3. The issue is not showing on previous AjaxControlToolkit releases: it starts to show up from november 2001 release. Page is working pretty fine with september 2011 release and all previous.
4. I don't really think that the error message is adequate in this case: besides, I don't want to turn off EventValidation or use RegisterForEventValidation to correct what should run fine without a patch like that.
I can provide all the code about this, but it's a large amount of code and I don't think it's necessary, at least for this initial report. Still pretty convinced there's something wrong going on behind the scenes of the toolkit at the moment.
If anyone is facing something related is welcome to join, any kind of advice is appreciated.
I have a pretty complex ascx control in a page. In this user control I have an update panel as a container of a TabContainer. I have a number of tabs on it, each of them hosting a GridView with many controls.
I have used toolkit release from september 2009 (30930) for a long time on this page, and all was running pretty fine till then.
When I tried to update AjaxControlToolkit to the latest release (may 2012) I started to face a really annoying issue: whenever I try to fire a GridView command on the first tab page freezes and I get error in subject. More precisely:
Sys.WebForms.PageRequestManagerServerErrorException: Invalid postback or callback argument. Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.
Please note the following:
1. The error is showed just for command events, I can still fire sorting commands on the gridview, and I can interact with the whole page without any other issue.
2. On any tab other than the first all works: commands are fired and executed just fine. Each time I return on first tab the issue shows up again, there's no difference between first load and following postbacks. GridViews inside tabs are engineered exactly in the same way and what's changing between them is just the datasource.
3. The issue is not showing on previous AjaxControlToolkit releases: it starts to show up from november 2001 release. Page is working pretty fine with september 2011 release and all previous.
4. I don't really think that the error message is adequate in this case: besides, I don't want to turn off EventValidation or use RegisterForEventValidation to correct what should run fine without a patch like that.
I can provide all the code about this, but it's a large amount of code and I don't think it's necessary, at least for this initial report. Still pretty convinced there's something wrong going on behind the scenes of the toolkit at the moment.
If anyone is facing something related is welcome to join, any kind of advice is appreciated.