'panes' is null or not an object

[Dave]

We are receiving a javascript error (see subject) when loading a user control that contains a splitter but only when the control is Ajaxed. While debugging, it is finding exception in ScriptResource.axd. The error is at the line: var l=n.panes;

}o.splitbars=k;
this._resetLastItemClass(g);
}},_fixItemsIndeces:function(e){var n=this._splitters[e];
var l=n.panes;
var d=l?l.length:0;
var q=n.splitbars;

This exception is new since we upgrade to Q3 2009. Is this a known issue? And as i said, we do not receive an error if Ajax is disabled. I can provide more code is necessary. Thanks!

[Dave]

Ok, I believe i have found out the circumstances that create the error and hopefully there is an easy fix.

Here is our situation:

I am creating a module for DotNetNuke. For this module, I have an Edit page, edit.ascx. On this page, i have a RadTab control and a placeholder. On each tab click, i dynamically load the associated ascx control and add it to the placeholder. Also on the edit page, there is an AjaxManager that ties the tab control and the placeholder together. As a result, the ascx controls are inherently ajaxed.

Now, 2 of those ascx controls have RadSplitter controls on them. When i click on a tab, the respective ascx control is loaded and if that ascx control contains a RadSplitter, there is an immediate javascript error, 'panes' is null or not an object. After that, my entire page is hosed. I have tried, one thing at a time, removing the inner content, splitter panes and settings until all i had left was just the Splitter control with only an id and runat server and no panes. And at that point, it was still causing an error. As soon as i remove the splitter, no more error (which was to be expected).

Now, here is where things get interesting. When the edit page is loaded for the first time (obviously via a postback from another page), the first tab is loaded, which does NOT have a splitter control. IF i put a splitter control on the first ascx control that is loaded on page load, then the other 2 ascx controls load just fine and the splitters work correctly. As soon as i remove the splitter from the first control, the other 2 break.

So there appears to be an issue with loading the splitter on a callback. If i have Ajax disabled for the page, everything works perfectly. This is just an issue with ajax and dynamically loaded controls.

Does that all make sense? For now, as a workaround, I've had to place an empty splitter control on the first control. Can you verify this? Is there a fix?

Thanks!

[Tsvetie]

Hi ApexUnited,
We are aware of this problem - it is a problem in the integration of RadSplitter and RadAjax (the problem should not appear with UpdatePanel) that was introduced with Q3 2009 SP1. We are currently working on it and there will soon be an internal build with the fix. I will post information here as soon as we upload such an internal build.

Regards,
Tsvetie
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.

[Chanan Zass]

Problem is not limited to Splitter.
We've encountered it with RadTabStrip, RadWindowManager and RadGrid.
All worked well with earlier versions of Telerik, but fail with 2009.3.

Hopefully this can be solved.

[Svetlina Anati]

Hello Chanan,

This exact error that "panes" is null or not an object could be related only to the RadSplitter control because this si teh collection of RadPanes and the other controls do not have such a collection. In case you experience problems with other RadControls, please open separate tickets for each separate control and share the relevant code to this exact control along with very detailed explanations of the error, its message text and screenshot of the debugger output and we will do our best to help.


Regards,
Svetlina
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.

[Chanan Zass]

I was not refering to "panes" but to the returned error message.
Our problems are obviously related to RadAjaxManager and the error regarding "is null or not an object."
Complex pages with, for example, RadWindowManager, a couple of grids, etc. now return this error, which was not there prior to 2009.3.

This is not a big issue, as we can always revert to earlier versions.
Anyhow, we'll open a ticket.

Merry Christmas.

[Svetlina Anati]

Hi Chanan,

In this case, I recommend to open separate tickets with the needed information because it is better to see what is wrong than to revert to an older version because if you do so you will not be able to take advantage of the improvements.

If the problems turned out really to be bugs, we will address them and we will also add Telerik points to your account for your kind cooperation.

If the problems are caused by configuration, we will help you resolve them.


Best wishes,
Svetlina
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.

[Dave]

Thank you for the response. I am glad to hear that you are aware of the issues. We'll be very interested in getting that new version.

Thank you!

[Tsvetie]

Hello ApexUnited and Chanan,
We have uploaded an internal build that features the fix you need. You can download it from your account - its version number is 2009.3.1221.

Best wishes,
Tsvetie
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.

[Chanan Zass]

Many thanks!
Amazing support.

I'm afraid this does not provide an answer to our problem.
We have a master page and an aspx page that loads a user control that include 2 radgrids, radeditor and radwindowmanager.
We've solved our problem by fixing our RadAjaxManager (in the master page) and RadAjaxManagerProxy (in our user control).
Should have done that before complaining.

Thanks much.

[Alex]

We are experiencing the same problem with RadSplitter after moving to 2009 Q3 SP1 release. Can we have access to this internal build to test if it resolves the problem for us?

[Tsvetie]

Hello Alex,
You can download the latest internal build from your account - in the Downloads section -> Latest Internal Builds. This build contains the fix you need.

Kind regards,
Tsvetie
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.

[Manmohan Rawat]

I am also facing same Problem.
Is this version "2009.3.1221" internal or it has been released for Paid Accounts(Registered) too ?
Please add this version in my account also. So that I can also check if this resolves my problem.

[Tsvetie]

Hi Manmohan Rawat,
Any customer, who can download Q3 2009 SP1, can download a latest internal build, built after this official release and before the next official release. We upload trial versions of the latest internal build as well, so that even in case you have not purchased a license, you can download this build. Please note, that in order to download an internal build, you need to have downloaded a current official release first. You can find detailed information on the latest internal builds here.

Please note that the 2009.3.1221 version was the first version that includes the fix. We regularly upload internal builds and any version that was uploaded after 21 December 2009 will include the fix as well.

Sincerely yours,
Tsvetie
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.

[XXXX]

I ran into this same error message using RadMultiPage, RadSplitter and RadPane when I was trying to solve the 100% issue .
A workaround that works for me is to put

RenderSelectedPageOnly

 

="false"

 

ont the MultiPageControl.

I will try to hold out until next SP or version.

Yours
   Björn