Hi,
A time ago i have updated my project with new Q1 2013, came from Q2 2012. After this version i have a strange bug with all controls. I have a big collection with radcontrols in one page (grid, toolbar, combo, treeview, tabstrip, windows etc), after some update/add/delete of my data in several radwindows, there will a huge error occur in your libraries but i cannot debug it.
What i will get after this error:
- All buttons in toolbar will lost their visibility state
- RadMenu will be hidden
- All columns in RadGrid will lost their widths
- Some combos will lost their values (which were bound in page load)
When this is occured, forcing a simple postback will occur a 500 server error without any message....
Have tried to turn off the RadCompression and RadAjax but with no result.
It seems RadScriptManager.registerclientscript will causes this, replacing this with normal clientscript have fixed my problem for a big part. But when i upload a image with async upload module will cause this again.
Happens with Q2 2013 as well, i'm working in Visual Studio 2012.
Do you know this problem?
A time ago i have updated my project with new Q1 2013, came from Q2 2012. After this version i have a strange bug with all controls. I have a big collection with radcontrols in one page (grid, toolbar, combo, treeview, tabstrip, windows etc), after some update/add/delete of my data in several radwindows, there will a huge error occur in your libraries but i cannot debug it.
What i will get after this error:
- All buttons in toolbar will lost their visibility state
- RadMenu will be hidden
- All columns in RadGrid will lost their widths
- Some combos will lost their values (which were bound in page load)
When this is occured, forcing a simple postback will occur a 500 server error without any message....
Have tried to turn off the RadCompression and RadAjax but with no result.
It seems RadScriptManager.registerclientscript will causes this, replacing this with normal clientscript have fixed my problem for a big part. But when i upload a image with async upload module will cause this again.
Happens with Q2 2013 as well, i'm working in Visual Studio 2012.
Do you know this problem?