Control interaction in Webparts

[Susan]

This one is a little bizarre, so forgive me if I don't describe this perfectly.

I'm in the process of updating custom web parts from our 2007 to 2010 deployment. For 2007, I had a Smartpart-style web part (ascx control wrapped in a web part class). For 2010, I'm taking advantage of the VS2010 Web Part projects (Visual Web Part in this case) and the native SP debugging.

The control for the webpart is designed around the following structure:

RadAjaxPanel
    RadTabStrip (2 tabs)
        RadMultiPage
            Pageview1
                 Formview (bound to ObjectDataSource)
            Pageview2
                 RadEditor

Due to databinding and speed concerns, the original web part was designed to use the RenderSelectedPageOnly option on the multipage. So with this setup, I'm experiencing the following behaviors:

1. When RenderSelectedPageOnly=false and the formview is in the display view, everything works great - editor loads content properly, allows editing correctly, etc.
2. RenderSelectedPage= false, Formview in Edit view - when you click on the tab to bring up the Editor, there is an outline around where the editor should be, but there is no content nor any controls.
3. When RenderSelectedPageOnly = true, the Editor does not display correctly, regardless of what mode the Formview is in.

Occasionally, with #2 and 3, the following javascript error displays momentarily:

Sys.ArgumentUndefinedException: Value cannot be undefined. Parameter name: type from ScriptResource.axd.

Any thoughts on what could be causing this strange series of behaviors?


ETA - I spent more time playing with this, and the problem seems to be with the Ajax controls (or at least how the editor is working with them). When I remove the AjaxPanel and just let the webpart go pure postback, everything works great. I then tried it with a RadAjaxManager instead of the panel, and the same behavior was displayed as with the panel. Wanted to include that info if that helps track this issue down.

[Iana Tsolova]

Hello Steve,

Could you please try using ASP:UpdatePanel instead of RadAjax and let me know if the issues persist?
Also, could you elaborate a bit more in the way you use the RadAjaxManager control to ajaxify the web part. Note that the RadAjaxManager should be placed in the application MasterPage and the ajax settings should be added dynamically on Page_PreRender of the web part.

All the best,
Iana
the Telerik team

[Susan]

I apologize for the delay in getting back to this...here are the results of the tests you suggested:

• Update Panel instead of RadAjaxPanel - identical behavior.
• RadAjaxManager on Master Page, settings in OnPreRender - identical behavior.

Any other suggestions to test out, or is there something else going on here that I'm missing? Thank you.

[Susan]

For what it's worth, I also just tested this with the 2010.826.35 release, and the behavior is identical.

[Iana Tsolova]

Hi Steve,

As the same behavior is observed with ASP:UpdatePanel instead of RadAjax, this means the issue is not cause from the RadAjax and we should look for it elsewhere. But to be able to find the exact source I will need to debug the issue and it would be great if you can send a sample replicating it.

Regards,
Iana
the Telerik team

[Susan]

Iana,

I have submitted ticket 343559 with a demo of the scenario I've described.

[Iana Tsolova]

Hi Steve,

Thank you for opetning a ormal support ticket. I will check it out and turn back to you with my findings.

Best wishes,
Iana
the Telerik team