This is a migrated thread and some comments may be shown as answers.
Splitter does not work in the DNN 7.2
3 Answers 13 Views
This is a migrated thread and some comments may be shown as answers.
Andy
Top achievements
Rank 1
Andy asked on 06 Mar 2014, 04:39 PM
Hello,

I am having DNN module which use RadSplitter. The module working correct in the DNN 7.1.
But when I have updated DNN to 7.2, the splitter stopped to work in the Internet Explorer (tested in the version 9, 10, 11).

The JS console display error.

Please see attached file.

I have tested also in the FireFox, the splitter works but console also display the same errror

3 Answers, 1 is accepted

Sort by
0
Andy
Top achievements
Rank 1
answered on 07 Mar 2014, 09:13 AM
Hello,

I am having DNN module which use RadSplitter. The module working correct in the DNN 7.1.
But when I have updated DNN to 7.2, the splitter stopped to work in the Internet Explorer (tested in the version 9, 10, 11).
Using Telerik.Web.UI.dll 2013.2.717.40

The module works correct when page in the Edit mode. But in the view mode does not.

The JS console display erros.

SCRIPT1004: Expected ';'
File: inspection-assettree.aspx, Line: 1707, Column: 13

SCRIPT5007: Unable to get property 'splitbars' of undefined or null reference
File: Telerik.Web.UI.WebResource.axd, Line: 11431, Column: 1


Please see attached file.

I have tested also in the FireFox, the splitter works but console also display the same errror
0
SwanB
Top achievements
Rank 1
answered on 07 Mar 2014, 10:46 AM
Hello,


I have also been seeing the excact same behavior, this hinders us from using the RadSplitter and I assume this is a change in the newer Telerik.Web.UI.dll's. We have tested also newer Telerik.Web.UI.dll ut no change.

/Swan
0
Vessy
Telerik team
answered on 11 Mar 2014, 01:17 PM
Hello Andy,

Th third thrown error is caused because the Splitter object found, which might be caused by the previous errors. Could you resolve the first two JavaScript errors and see whether the  Splitter-related error will persist? I yes, could you try to isolate the issue outside the DNN environment and send it for a further investigation?

If the issue cannot be reproduced in a stand-alone project, I would suggest you to post your question in the DNN forums and contact the support of DNN for help in case there aware of a previous version functionality or customization, that might be causing the issue in DNN 7.2.

Regards,
Vessy
Telerik

DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.

Asked by
Andy
Top achievements
Rank 1
Answers by
Andy
Top achievements
Rank 1
SwanB
Top achievements
Rank 1
Vessy
Telerik team
Share this question
or