Microsoft Ajax CDN is not working

Posted by Community Admin on 04-Aug-2018 21:46

Microsoft Ajax CDN is not working

All Replies

Posted by Community Admin on 24-Mar-2012 00:00

I have a SF 5.0.2523.0 sample site.
When I turn on Enable CDN under Administration\Settings\Advanced\Pages\Script Manager and recycle the website, the installation renders with unusable backend interface.
After researching the problem it seems that out of the box SiteFinity is using a customized version of MicrosoftAjax.js. So when it tries to load the original js version from, it fails to parse it. The customized version in that SiteFinity uses has changes in the encoded strings for Sys.Res set at the end of the file. More specifically the customized version is using double qoutes instead of single qoute for strings and has some values unicode encoded.
Is there a way to enable the Ajax CDN and still have the backend rendering fine?

Posted by Community Admin on 24-Mar-2012 00:00

Bad news :/  I don't think I've ever been able to get the CDN options in the backend to work...It's gotta be in PITS somewhere though to vote on.

Posted by Community Admin on 25-Mar-2012 00:00

Problem is that Ajax is just not loaded correctly in this case. So it is not only the backend that is affected though it is the most easiest to see. If that is the case I would say CDN is just not supported in this version.

Posted by Community Admin on 26-Mar-2012 00:00

Oh yeah sorry I don't just mean in the backend, I mean SET in the backend options, but yeah, try turning any CDN on (not just the msajax one)...they don't play very nice at least the last time I tried it I think in 4.4.

Posted by Community Admin on 26-Mar-2012 00:00


If I may correct you a tiny bit and expand on the issues...
when enabling the 'CDN' option it does not try to load the original Ajax - but the beta release on which Sitefinity customized on. And that's where trouble starts...

The Telerik.Web.UI parts rely on the 'release' version of MicrosoftAjax and Sitefinity relies on the 'beta' version. Normally when not utilizing the CDN option, you'll see the RadControl parts loading the release MicrosoftAjax and afterwards you'll see Sitefinity load the customized version.

Fun fact:
The 'beta' CDN version and the embedded resource 'customized' version aren't the same. So even if we got around loading the 'release' version first, we'd still miss out on the customized parts.

In case you find a way around the MS Ajax incompatibility, you'll notice they still haven't fixed the extra '.' in the jQuery CDN. (

Nor will the solve the double loading of jQuery. (RadControls use v1.6.4, Sitefinity uses 1.7.1).

jQuery UI
And lastly the back end relies heavily on jQuery UI but they haven't provided any CDN paths for this... why? Because Sitefinity did the same for jQuery UI as with Microsoft Ajax and provided Telerik.Sitefinity.Resources.Scripts.jquery-ui-1.8.8.custom.min.js 

So +1 in agreeing CDN doesn't function...


Posted by Community Admin on 26-Mar-2012 00:00

post scriptum

When 'enable CDN' is turned on, the following scripts get loaded twice on a backend page like for instance 'page overview':

/* START Telerik.Sitefinity.Resources.Scripts.jquery.clickmenu.pack.js */
/* START Telerik.Sitefinity.Web.Scripts.IAsyncCommandReceiver.js */
/* START Telerik.Sitefinity.Web.Scripts.RadGridBinder.js */
/* START Telerik.Sitefinity.Web.Scripts.PromptDialog.js */
/* START Telerik.Sitefinity.Web.UI.Fields.Scripts.IField.js */
/* START Telerik.Sitefinity.Web.UI.Validation.Scripts.Validator.js */
/* START Telerik.Sitefinity.Web.UI.Fields.Scripts.FieldControl.js */
/* START Telerik.Sitefinity.Resources.Scripts.xregexp-min.js */
/* START Telerik.Sitefinity.Resources.Scripts.xregexp-unicode-base.js */
/* START Telerik.Sitefinity.Web.UI.Fields.Scripts.TextField.js */
/* START Telerik.Sitefinity.Web.UI.Fields.Scripts.FieldDisplayMode.js */
/* START Telerik.Sitefinity.Web.UI.ItemLists.Scripts.ItemsList.js */
/* START Telerik.Web.UI.ListView.RadListViewScripts.js */
/* START Telerik.Sitefinity.Web.Scripts.Pager.js */
/* START Telerik.Sitefinity.Web.Scripts.RadListViewBinder.js */
/* START Telerik.Sitefinity.Web.UI.ItemLists.Scripts.ItemsTreeTable.js */
/* START Telerik.Web.UI.TreeView.RadTreeViewScripts.js */
/* START Telerik.Sitefinity.Web.Scripts.RadTreeBinder.js */
/* START Telerik.Sitefinity.Web.Scripts.DecisionScreen.js */
/* START Telerik.Sitefinity.Web.UI.Backend.Elements.Widgets.Scripts.DateFilteringWidget.js */
/* START Telerik.Sitefinity.Resources.Scripts.jquery-ui-1.8.8.custom.min.js */
/*  * jQuery UI 1.8.8
/*  * jQuery UI Widget 1.8.8
/*  * jQuery UI Mouse 1.8.8
/*  * jQuery UI Position 1.8.8
/*  * jQuery UI Draggable 1.8.8
/*  * jQuery UI Droppable 1.8.8
/*  * jQuery UI Resizable 1.8.8
/*  * jQuery UI Selectable 1.8.8
/*  * jQuery UI Sortable 1.8.8
/*  * jQuery UI Accordion 1.8.8
/*  * jQuery UI Autocomplete 1.8.8
/*  * jQuery UI Button 1.8.8
/*  * jQuery UI Dialog 1.8.8
/*  * jQuery UI Slider 1.8.8
/*  * jQuery UI Tabs 1.8.8
/*  * jQuery UI Datepicker 1.8.8
/*  * jQuery UI Progressbar 1.8.8
/*  * jQuery UI Effects 1.8.8
/*  * jQuery UI Effects Blind 1.8.8
/*  * jQuery UI Effects Bounce 1.8.8
/*  * jQuery UI Effects Clip 1.8.8
/*  * jQuery UI Effects Drop 1.8.8
/*  * jQuery UI Effects Explode 1.8.8
/*  * jQuery UI Effects Fade 1.8.8
/*  * jQuery UI Effects Fold 1.8.8
/*  * jQuery UI Effects Highlight 1.8.8
/*  * jQuery UI Effects Pulsate 1.8.8
/*  * jQuery UI Effects Scale 1.8.8
/*  * jQuery UI Effects Shake 1.8.8
/*  * jQuery UI Effects Slide 1.8.8
/*  * jQuery UI Effects Transfer 1.8.8
/* END Telerik.Sitefinity.Resources.Scripts.jquery-ui-1.8.8.custom.min.js */
/* START Telerik.Sitefinity.Resources.Scripts.jquery-ui-timepicker-addon.js */
/* * jQuery timepicker addon
/* END Telerik.Sitefinity.Resources.Scripts.jquery-ui-timepicker-addon.js */
/* START Telerik.Sitefinity.Web.Scripts.UserPreferences.js */

Posted by Community Admin on 31-Jul-2012 00:00

I can confirm that this PITS issue ( is still a problem with that latest version 5.1

Posted by Community Admin on 24-Aug-2012 00:00

Just wanted to write that this post helped me getting my back-end running again. 
Realy was a site saver that post.


This thread is closed