Javascript debugging

7 posts, 1 answers
  1. SolutionStream
    SolutionStream avatar
    40 posts
    Member since:
    Apr 2009

    Posted 30 Nov 2009 Link to this post

    I have a new crash that happens in the Scheduler javascript code that I'm not sure how to begin debugging.  Are there suggestions that you guys use that you could share with me?

    This is the type of error that shows in the IE 8 error window: 
    Webpage error details 
     
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2) 
    Timestamp: Mon, 30 Nov 2009 22:56:17 UTC 
     
     
    Message: '0.tBodies.0.rows[...].cells' is null or not an object 
    Line: 6438 
    Char: 2 
    Code: 0 
    URI: http://localhost/Pinnacle/Telerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl00_ctl00_MainContent_MainContent_radScriptManager_HiddenField&compress=1&_TSM_CombinedScripts_=%3b%3bSystem.Web.Extensions%2c+Version%3d3.5.0.0%2c+Culture%3dneutral%2c+PublicKeyToken%3d31bf3856ad364e35%3aen-US%3ad0c4ca6e-6b5d-49b6-922d-5244924fb100%3aea597d4b%3ab25378d2%3bTelerik.Web.UI%2c+Version%3d2009.2.701.35%2c+Culture%3dneutral%2c+PublicKeyToken%3d121fae78165ba3d4%3aen-US%3a7e598a31-3beb-49a1-914c-5f530240f0ea%3a16e4e7cd%3aed16cbdc%3a874f8ea2%3af7645509%3a24ee1bba%3a19620875%3a39040b5c%3af85f9819%3a650fdad%3a41a6cee9%3ad40f7d5c%3a431f16a4%3a1a9ac27f%3a7d98db04%3afe65db44%3a63767fed%3a44e9d927%3a26c790aa%3a3cdff5d5%3ae91ff703%3a7666c7ed%3aef9d9f4a%3aa960fda2%3ab7778d6c%3a8674cba1%3ac08e9f8a%3aef347303%3aa51ee93e%3a1e771326%3aaa288e2d%3ae085fe68%3a59462f1 
     

  2. Datamex
    Datamex avatar
    161 posts
    Member since:
    Jun 2012

    Posted 01 Dec 2009 Link to this post

    Try using Firefox in combination with the plugin "Firebug". This gives you debug options for javascript. It even supports breaklines and such.
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. SolutionStream
    SolutionStream avatar
    40 posts
    Member since:
    Apr 2009

    Posted 01 Dec 2009 Link to this post

    Unfortunately, I believe this particular crash is beyond firebug.  I have downloaded the source to the 2009.3.1103 build and have built it in debug following the instructions found the in the instructions.pdf included with the source, but when I hit the exception I still see all the javascript compressed into one line like the release version.

    Is there an extra step to get VS to use the source js files?
  5. Schlurk
    Schlurk avatar
    812 posts
    Member since:
    May 2009

    Posted 02 Dec 2009 Link to this post

    I think the best thing to do would be to describe exactly what you are trying to do, perhaps there's an issue with your implementation that is causing this javascript error to be thrown.

    On the same note as Datamex had you can also try out Telerik's new JustCode tool, it's pretty nifty and helps out a lot with javascript :)
  6. Roatin Marth
    Roatin Marth avatar
    65 posts
    Member since:
    Nov 2007

    Posted 28 Jan 2010 Link to this post

    I'm seeing this javascript error as well from time to time. Often in IE6.
    I've just added a new appointment to my schedule and switched to week view or day view. Switching back to month view gives me this error in some compressed telerik javascript file.

    has anyone made any headway with this? What are some things that would cause this issue?

    regards,

    Roatin
  7. Answer
    Peter
    Admin
    Peter avatar
    6637 posts

    Posted 28 Jan 2010 Link to this post

    Hello Roatin,

    This problem should be fixed with service pack 2 - version 2009.3.1314.

    Regards,
    Peter
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  8. SolutionStream
    SolutionStream avatar
    40 posts
    Member since:
    Apr 2009

    Posted 28 Jan 2010 Link to this post

    This is true,
    2009.3.1314 fixed this for us.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017