Hello,

Have you tried to run the offline sample on WebGrid/WebCombo?

I've tried to run the attached sample and it works fine on my end without any javascript error.

Could you try to run the attached sample and see how it works on your end?

It is difficult to reproduce the issue in here, therefore, if you can guide me on how to get the error, that would be helpful. Or, is there any simple sample that you can provide for me to test?

Thank you.

Regards,
-Martin-

Martin,

I tried your example and I didn't get the same errors.  So, I created a working example of what I'm seeing.  I noticed a couple of things.  I am able to reproduce the scripting running slow issue.  The problems seems to be the RowChecker column.  I currently have the test to maxcount = 1000 and when you click on RowChecker header OR one row you get the script running slow message.  If I change the maxcount = 30 records, I don't get this problem.  In the code behind of the example you can change the maxcount. 

My other question is we have one developer that just received a new box and you all released the current 2011 IS controls.  In this WebCombo 5 is shown for them as well as the Essential.  Everyone else upgraded their controls through the upgrade manager.  WebCombo said it had an update but it didn't show the WebCombo 5 verions/js/dlls.  Why is this?

Hello,

Could you tell me how slow the script was running?

If it's possible, could you provide a simple working sample that replicates your issue? It would be easier for me to trace the error if I can get a sample that can be tested on my end.

When you upgrade WebCombo from Update Manager, it will automatically update the assembly along with the js files in your [Installation folder]\Intersoft Solutions\WebUI Studio for ASP.NET\WebCombo.NET 5.0\Bin.

Open the folder, right-click on ISNet.WebUI.WebCombo.dll and select Properties. Switch to Details tab and check the File version. It should be 5.0.7200.2, which is the latest build for WebCombo 5. You can check the version history from here.

Hope this helps. Thank you.

Regards,
-Martin-

Martin,

I provided he example (testc.zip) and steps of how to reproduce in my previous response regarding the error script running slow.  I provided you with the steps as well from the response:

"The problems seems to be the RowChecker column.  I currently have the test to maxcount = 1000 and when you click on RowChecker header OR one row you get the script running slow message.  If I change the maxcount = 30 records, I don't get this problem.  In the code behind of the example you can change the maxcount."

This is a big problem for us, because that we had to role back our upgrade because of this script issue.  We use the RowChecker on several of our grids.  I've included a screenshot of the error using the code above from testc.zip.

As far as the upgrade, I looked at the versions of the computers before sending the question and they all show WebCombo 4.0.7200 and the update manager shows no update for WebCombo.  It acts like it's been updated. 

I’m afraid that this problem seems to be related to the browser version that is used to open the page. I tried to reproduce this problem in my local test by using several browser versions such as: IE 8; IE 9; Mozilla Firefox 5; and Google Chrome 12. The issue is only replicable in IE 8.

You can try to either upgrade or change the browser version which is used to view the page; or by reducing the PagingSize to a smaller number.

Hope this helps.

Yudi,

Our clients use IE 8.  This wasn't a problem before the upgrade.  You can still get this error when you have a pagesize of 30 with the rowchecker column.  In order to stop the javascript error I have to go down to a pagesize of 23 (pagesize>= 24 produces the error see screenshot ErrROwChecker24Rows.zip).  Without this column, I can use our normal pagesize of 500.  This cannot be right?  Are you all not supporting IE 8?  The problem seems to be the rowchecker and I notice you all made a change to the rowchecker for this latest release.

Yudi,

Is anyone looking into this? 

Hello,

I have tested the project. So far, I couldn't assume this issue is a regression bug yet.

I have reported this issue to the developer team to be investigated as soon as possible.

We'll just need to wait for their response and hopefully they are able to come up with a good solution for you.

I will keep you informed about the update.

Thank you.

Regards,
-Martin-

Hello,

A nightly hotfix build has been sent to your email.

Please check your inbox for more information and apply the hotfix to test whether the issue is already fixed or not.

Thank you.

Regards,
-Martin-

Martin,

I tried the hotfix and this is still an issue. 

Hello,

The issue doesn't occur in IE9. Does the issue occur when you do sorting / grouping? Does the error occur when you select row using RowChecker?

I have reported this issue again to the developer team. Maybe they missed something on the previous fix.

I will ask my colleague, Yudi to test the hotfix on his end as well, since he is using IE8 in his environment.

I will keep you inform with the update.

Thank you.

Regards,
-Martin-

Martin,

This happens when you have have a RowChecker column on a grid.  If you click "all" on the RowChecker column you get this scripting issue.  Our clients are using IE 8.  Please see previous posts.  I've given detail descriptions.  Thanks you!

I uploaded a video file in here that shows how the testc.aspx sample file which was sent and attached in your previous message run on Internet Explorer 8 browser using the nightly build of WebGrid 7 build 431.

The issue is no longer persist when user click the row checker checkbox. Please kindly let us know if you have different result.

Yudi,

I saw your video showing that it works on your end, but we're still having the issue on our end.   So, I created a video.  Click here for the link.  The start of the video shows getting the files from the WebGridNET7_0_7200_431.zip file you sent me for the nightly hotfix build, extracting the contents to a WebGridNET7_0_7200_431 folder, moving the files to the common areas of Intersoft solutions folder, and deployment of them.

Thanks,

Tenika

I sent you a message to your registered email account that shows step-by-step to get the latest nightly build of WebGrid.NET 7.0 and WebUI.NET Framework 3.0. Kindly check your inbox and let us know if you have different result.

Yudi,

I just got a chance to view your information and I'm still seeing the same error.  I followed the directions from the link you sent as well regarding applying HotFixes.  I've sent you a another video showing what I'm seeing.  Click here to view file named QuickMeeting-20110720.  I start out the video showing you the GAC where I have added the new files.  Next I show you files I downloaded from your skydrive and installed them.  I compare them by the dates and versions.  Then finally I run the sample testc.aspx and I still get the javascript error.

Tenika.

Hi Tenika,

I am having some similar issues at you. mainly arround the grouping and expansion  2000 - 3000 rows data.

used to be quite quick now runs like a dog or scripting issue.

If you use doctype

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

instead of

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

under IE8 you should see the slow running script error not appearing. (still slow though)

hopefully they will fix this for

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

Peter,

Thanks for the tip.  I used the following and it did cause the scripting issue to be removed; however the formatting of my grids are off.  Are you having the same issue?

Martin/Yudi,

I added an example of my Test page (testc.aspx/testc.aspx.cs) in my zip file.

Hello there,

I believe the slow script has been fixed if you are using the following DocType:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >

<html>

However, what kind of error did you get for your WebGrid's formatting? Could you provide a screenshot for better visualization?

Thank you.

Regards,
-Martin-

Hi Tenika,

Please try to apply the solution suggested by Martin and let us know whether it helps or not.

Thank you.

This is still not working and lining up correct.  I have attached a screenshot of what I'm seeing.

Thank you for your prompt response.
I will forward your feedback to the development team for further investigation.