AJAX Controls Not Working Properly On New Install - CalendarExtender For Example

Topics: General, Installing BugNET
Apr 11, 2013 at 2:03 PM
After looking around at the competition I decided to install BugNet on a sub-domain as I really like it. Very clean and fresh looking. Well done guys. I have spent some time setting up a couple of projects and apart from POP3 not working all was looking well.

However, while running FireBug to try and determine why POP was failing I noticed some other JS errors being reported in the background. These all relate to the AJAX Toolkit controls used like the "CalendarExtender" control in "PickDate.ascx". I had not realised that this control was supposed to enable a calendar to popup for date selection (which on my installation it does not - I just get the Icon to the right of the text box). The error being reported is:

SCRIPT5007: Unable to get property 'UI' of undefined or null reference

and appears to revolve around generated code like:
$create(Sys.Extended.UI.CalendarBehavior, {"button":$get("ctl00_ctl00_MainContent_Content_JumpToDate_imgCalendar"),"id":"ctl00_ctl00_MainContent_Content_JumpToDate_CalendarExtender1"}, null, null, $get("ctl00_ctl00_MainContent_Content_JumpToDate_DateTextBox")); 
It would appear the call to "Sys.Extended.UI.CalendarBehavior" is failing as "Sys.Extended" does not exist in the DOM. This suggests to me that something has not initialised the "Sys.Extended" object and from googleing it would suggest the Script Engine is at fault here. Checking the various master pages etc, it does appear to be being referenced, all be it via a master page and not the control. Visual Studio certainly does not complain as I downloaded the Source to try and debug what is happening.

I therefore assume that something is probably misconfigured in web.config but don't know what as the AJAX Toolkit references have not changed. The web.config I am using is as per the Install package bar tweaks to connection string and localisation for the UK.

The "CalendarExtender" is not the only control failing, but as the errors are similar, fixing this should resolve all the others. Any pointers of help would be much appreciated.

Regards, Andrew.
Apr 11, 2013 at 2:44 PM
I should also point out this is not a client side issue as I have tried IE 10 and FF 19 & 20.