Potential Bug with Q2 Scheduler (Page_Validators is undefined)

8 posts, 0 answers
  1. Jim
    Jim avatar
    23 posts
    Member since:
    Nov 2007

    Posted 13 Jul 2009 Link to this post

    Hello,
    I have a project initial developed using 2009 Q1.  It is a DNN module (using DNN 4.9).  Things worked perfectly until after the upgrade to Q2.   I am now receiving an error Page_Validators is undefined... blah blah... http://localhost/DNN/ScriptResource.axd. 

    It only happens on Insert when the options are clicked and when editing an existing appointment.   I am aware of an issue with DNN 4.8 in this regard, and was faced with a null is null error until I upgraded to 4.9.  After that it worked perfectly until after the Telerik Q2 release.  To simplyy things I created a new module that is an exact copy of the RadScheduler DNN module provided by telerik.   It too gets the same error under the same conditions.

    Please advise.  Is this a bug or did I miss something while upgrading?
  2. Jim
    Jim avatar
    23 posts
    Member since:
    Nov 2007

    Posted 13 Jul 2009 Link to this post

    In further debuging I have also run across the null is null or not an object error with the ScriptResource.axd.   I originall incountered this with Q1.  The root cause was with a DNN 4.8 bug.    I upgraded to 4.9 and the issue went away.  It has now returned with the new Q2 Release.    So in short,  I am seeing two errors that seem to interchange at random.  Either null is null or Page_Validators is undefined
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. T. Tsonev
    Admin
    T. Tsonev avatar
    2772 posts

    Posted 13 Jul 2009 Link to this post

    Hi Jim,

    This is really strange - the code that seems to be causing this error is not changed between the two versions. For some reason the ASP.NET validation scripts are not getting loaded.

    We've added a check so at least the code will not throw an error, but it's likely that the validators in the advanced form will not be functional. The fix will be available in the next internal build tomorrow (version 2009.2.713 and up), so you can give it a try and let us know if this is the case.

    Best wishes,
    Tsvetomir Tsonev
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  5. Jim
    Jim avatar
    23 posts
    Member since:
    Nov 2007

    Posted 14 Jul 2009 Link to this post

    debug update:
    I did mention that in my initial testing that I created a new user control that is an exact copy of the demo and it too was seeing the error.  That was only partially true.  I simplified the one Rad Scheduler within the control to match, but there were other components.  When I created a user control that was not a dnn module, and ran it outside the dnn framework, I did not see the error.  This user control only contained the Rad Scheduler and nothing else.   I then converted it to a dnn module and ran it within dnn it worked.  So I then slowly, one component, method, etc at a time (adding most likely causes first) converted the new module to look like the one with the error.  Thus far no problems.  I wanted to give status on this now, as it does not appear to be a Telerik problem.  I am not sure when I will have time to trace the error to the root cause, but it will be before this weekend.  Unfortuantly VS debugger does not pick this up,  I will checkout Telerik's new debugger to see if it sheds any light.
  6. Jim
    Jim avatar
    23 posts
    Member since:
    Nov 2007

    Posted 15 Jul 2009 Link to this post

    Update and Resolved.

    First I found the problem on my end.  Second, the new build does catch the error and subsequetly prevents that specific javascript error from occuring, however, an object expected error occures, assumabaly when it tries to reference the validator.  I concider that a non-issue.  The fact is, it is strange that the validator could not be loaded.  I have traced the issue to the trigger within my code.

    I created a custom control that contained a Rad Scheduler.  I added my custom control in a RadPageView under a tab.  I also have a RadAjaxManager where I set the Ajax Setting to the custom control an assign a Loading Panel. In addition, within the Custom Control, I have a RadAjaxManagerProxy,  The Ajax settings and updated controls here are the schedule itself.   Apparently this caused some kind of conflict.   I was unable to trace it to the point where I can tell you exactly what and how it broke, but tracing it to this point is good enough for me
  7. T. Tsonev
    Admin
    T. Tsonev avatar
    2772 posts

    Posted 16 Jul 2009 Link to this post

    Hi,

    I have a suspicion about the cause of the problem. The ASP.NET validators are not AJAX controls and they don't register their scripts through the ScriptManager. As you're showing the scheduler with an AJAX request, their scripts are not getting loaded.

    My suggestion is to place a validator on the page and hide it in a div with display:none. Any type should do, just set its ValidationGroup to something that is not used on the page, so it'll not actually validating anything.

    I hope this helps.

    Greetings,
    Tsvetomir Tsonev
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  8. Jim
    Jim avatar
    23 posts
    Member since:
    Nov 2007

    Posted 16 Jul 2009 Link to this post

    It is always good to understand the root cause and not just the scenarios that trigger it.   There was no need to use Ajax, and by removing this as a managed control solved the problem.   To help verify your suspesion, I did a quick test as you outlined.  You are right.

    Thanks
  9. Des
    Des avatar
    12 posts
    Member since:
    Jan 2009

    Posted 03 Aug 2009 Link to this post

    Thanks for this solution guys, I had the same problem with Scheduler after enabling AJAX and by adding a dummy validator it has fixed the problem.

    Des Owen
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017