RadFileExplorer with RadAjaxManagerProxy gives javascript error

[Suzy]

Hi,

I have a RadFileExplorer in a page using a masterpage and using RadAjaxManagerProxy.

When I add a folder or delete on I get a javascript error : Value must not be null for Controls and Behaviors.

When I remove the RadAjaxManagerProxy, I do not get this error. 

What is the problem?  I need the RadAjaxManagerProxy.

Part of my code:

<asp:Content ID="Content2" ContentPlaceHolderID="cphContent" runat="server">

    <telerik:RadAjaxManagerProxy ID="RadAjaxManagerProxy1" runat="server">
       <AjaxSettings>
           <telerik:AjaxSetting AjaxControlID="updContent">
               <UpdatedControls>
                    <telerik:AjaxUpdatedControl ControlID="updContent" LoadingPanelID="radAjaxLoadingPanel" />
                   <telerik:AjaxUpdatedControl ControlID="FileExplorer1" />
               </UpdatedControls>
           </telerik:AjaxSetting>
       </AjaxSettings>
    </telerik:RadAjaxManagerProxy>

    <asp:Panel ID="updContent" runat="server" >
        <telerik:RadFileExplorer runat="server" ID="FileExplorer1" Width="520px" Height="500px" CssClass="rfeFocus" AllowPaging="true" PageSize="10" ExplorerMode="FileTree" VisibleControls="ContextMenus,Toolbar,TreeView">
            <Configuration EnableAsyncUpload="true" ></Configuration>
        </telerik:RadFileExplorer>
    </asp:Panel>
</asp:Content>

Kind regards

Suzy

[Vessy]

Hello Suzy,

Such behavior is expected when a FileExplorer control is updated via AJAX. Please, note that FileExplorer's functionality is heavily based on client-side callbacks and it is highly not recommended to be externally ajaxified. That's why the error is not observed when the AjaxManagerProxy is removed.

The reason behind this limitation is that two AJAX requests are initiated at the same time and respectively they are canceling each other, blocking the proper FileExplorer functioning. Unfortunately, this is a limitation that stems from the AJAX Framework and we are not in position to suggest you any suitable workaround (except for disabling the external updating of FileExplorer).

Regards,
Vessy
Telerik

 

 

[Suzy]

Vessy,

what do you mean by 'except for disabling the external updating of FileExplorer'?

regards

Suzy

[Vessy]

Hi Suzi,

Sorry for not being clear enough in my previous reply.

By saying 'except for disabling the external updating of FileExplorer' I was referring the explanation from the first paragraph, confirming the observation made by you that FileExplorer is working properly when the RadAjaxManager proxy is removed. In short -  removing FileExplorer from the AjaxManagerProxy updated controls list should fix the undesired behavior.

Regards,
Vessy
Telerik

 

 

[Suzy]

One more question

How do I remove the FileExplorer from my AjaxManagerProxy?
The Fileexplorer is implemented in my page within the AjaxManagerProxy because all the other actions needs to be ajaxified.
Is there a way to remove the object (my Fileexplorer) from the AjaxManager controls list?

in attachment an example of how my page looks like

[Vessy]

Hi Suzy,

I am afraid that there is no property removing only one single control from the AjaxControl definitions in case any of its parents is being updated. As the idea of the AJAX Postbacks is to make only partial updates, avoinding the whole page update, you have to add the controls that have to be updated to the RadAjaxManager/RadAjaxManagerProxy updated controls declarations. If a control is configured as updated control it will update all controls inside itself, I would advice that you review in details the RadAjaxManager documentation section.

For example, in the provided in your first post code snippet both confiugurations are updating FileExplorer and has to be removed. Note also that updating child control and its parent in one and the same time is hardly not recommended because it will lead to nested Ajax request which will cancel each other.

I hope this information will be helpful for you.

Regards,
Vessy
Telerik