I am still on the search to use RadAjaxManager in SharePoint.
I've tried to put a simple inside an ASCX which is loaded by a webpart.
| <radA:RadAjaxManager ID="RadAjaxManager1" runat="server"> |
| </radA:RadAjaxManager> |
strange results occur. The HTML for page gets corrupted if I add this:-
| Welcome root<script type="text/javascript" language="javascript">var _spUserId=1;</script>"Search Scope""Enter search words""Go Search""Go Search"<HTML xmlns:o="urn:schemas-microsoft-com:office:office" dir="ltr"> |
| <HEAD><.... blah, blah |
Without the RadAjaxManager the html is fine.
Has anyone else tried this.... got the same results?
Martin
11 Answers, 1 is accepted
We are sorry for the delayed reply. We reproduced the problem and debugged the MOSS controls for some time. We finally discovered that the problem appears, because SharePoint (WSS v3 and MOSS) uses cache substitutions extensively on its pages. RadAjax unfortunately, does not support that, and that is why the pages break when you place a RadAjaxManager control.
We have been unable to find a workaround yet, but we discovered that you can safely use the RadAjaxPanel control instead. The panel will not interfere with cache substitutions unless you place a substitution control inside, which seems unlikely.
Regards,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I need the RadAjaxManager because I need changes to be made to other Web Parts. AjaxPanels will only allow changes to be made on it's own Web Part.
I would guess this might be a common scenario for SharePoint Web Part developers who wish to employ Ajax. Any developments on this I will be most interested.
Thanks,
Martin
We will continue to investigate the issue and you can be sure, that when we find a workaround, we will update RadAjax so it is fully compatible with MOSS/WSS v3.
All the best,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I'd like to programmatically add a RadAjaxManager to allow a Calendar (in a UserControl) to provide the SelectedDate to another UserControl.
I have created the controls in the CreateChildControls() event (including the RadAjaxManager) and then wire up the AjaxSettings after a call to RenderChildren(writer) in the Render(...) event. However the page seems to post-back rather than "Ajax".
Unfortunately, we still have not solved the problem with RadAjaxManager and cache substitutions. You can only use the RadAjaxPanel control in MOSS.
All the best,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Please let me know if there are any updates on using RADAjaxManager with custom SharePoint webparts.
Regards
Sunil
We've been unable to make AjaxManager work with cache substitutions. Please use the RadAjaxPanel control instead for the time being.
Greetings,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I am afraid not - the restrictions in WSS do not allow the usage of RadAjaxManager.
Kind regards,
Georgi Tunev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Hi,
I am using RadAjaxPanel inside a web-part and have configured the panel to load 300ms after the page load. The complete page is using a MOSS policy for output caching for anonymous users but the RadAjaxPanel has personalized content. I therefore want the contents inside the panel to not be cached. The purpose of the RadAjaxPanel was to not cache the contents. Currently, they are getting cached leading to unwanted results. Can I set the
Response.Cache.SetCacheability(HttpCacheability.NoCache)
inside the code that is loaded asynchronously by the panel to achieve this?
I noticed that this issue is only on controls which have view state enabled.
FYI, user control level output substitution does not seem to work in MOSS at all; it is simply ignored, it seems. That is the reason for trying to use a RadAjaxPanel that loads asynchronously after the whole page loads.
Thanks.
Sandeep.
I'd suggest that you temporarily disable Ajax on your page (set EnableAjax=False and Response.Cache.SetCacheability(HttpCacheability.NoCache)) and make sure that your approach works with PostBacks. Once you have the visibility code working with PostBacks, you can re-enable Ajax and everything should work fine. This is a good debugging approach to take when you're concerned that Ajax is causing problems.
Hope this helps...
<John:Peel />